Technologies for integrating cloud content items across platforms

ABSTRACT

Systems and methods for integrating cloud-based and cloud-backed content items with a content management system are provided. In some examples, a method can include receiving a request to open a content item using a client application at a first client device; detecting that the content item is open at a second client device from a different client application that supports live collaboration; and directing the first client device to an instance of the different client application at the first client device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of, and priority to, U.S.Provisional Patent Application No. 62/756,367 filed on Nov. 6, 2018,entitled “TECHNOLOGIES FOR INTEGRATING CLOUD-BASED DOCUMENTS ACROSSPLATFORMS”, the contents of which are hereby expressly incorporated byreference in their entirety.

This application is also related to U.S. Non-Provisional patentapplication Ser. No. ______, Attorney Docket No. P1328US1_085118-613050,filed on Sep. 25, 2019, entitled “TECHNOLOGIES FOR INTEGRATINGCLOUD-BASED DOCUMENTS ACROSS PLATFORMS”; U.S. Non-Provisional patentapplication Ser. No. ______, Attorney Docket No. P1328US2_085118-637451,filed on Sep. 25, 2019, entitled “TECHNOLOGIES FOR INTEGRATINGCLOUD-BASED DOCUMENTS ACROSS PLATFORMS”; U.S. Non-Provisional patentapplication Ser. No. ______, Attorney Docket No. P1328US3_085118-633792,filed on Sep. 25, 2019, entitled “TECHNOLOGIES FOR INTEGRATINGCLOUD-BASED DOCUMENTS ACROSS PLATFORMS”; U.S. Non-Provisional patentapplication Ser. No. ______, Attorney Docket No. P1328US5_085118-633797,filed on Sep. 25, 2019, entitled “TECHNOLOGIES FOR INTEGRATINGCLOUD-BASED DOCUMENTS ACROSS PLATFORMS”; and U.S. Non-Provisional patentapplication Ser. No. ______, Attorney Docket No. P1328US6_085118-633798,filed on Sep. 25, 2019, entitled “TECHNOLOGIES FOR INTEGRATINGCLOUD-BASED DOCUMENTS ACROSS PLATFORMS”; the contents of which arehereby expressly incorporated by reference in their entirety.

TECHNICAL FIELD

The present technology pertains to integration of cloud content itemswith distributed storage, collaboration and synchronization systems.

BACKGROUND

Cloud storage systems allow users to store and access data on the cloud.A cloud storage system can allow users to maintain a variety of contentitems stored on, and accessible from, a single cloud storage system.Some cloud storage systems allow users to share data with other usersand access the data in a collaborative fashion. Moreover, some cloudstorage systems may also support synchronization of copies of dataacross a number of client devices and servers so each copy of the datais identical and locally accessible from the client devices. Thesynchronization functionality can enable users to store local copies ofthe data on their client devices and access the local copies of the datafrom their client devices. The local copies of the data can besynchronized with the data on the cloud storage systems to ensureconsistency between local and cloud copies of the data. The local copiesof the data may provide users with faster access to the data and mayallow users to access the data when their client devices are offline.

Increasingly, users are using a variety of cloud-based or cloud-backedcontent items and applications from different cloud-based services.Often, such cloud-based or cloud-backed content items are stored acrossseparate cloud storage systems associated with the different cloud-basedservices. Many of such cloud-based applications do not operate ontraditional files, instead operating on the cloud-based content items,which are typically designed specifically for the cloud-basedapplications. For example, the cloud-based content items may havespecific formats and functionalities that may only be supported byspecific cloud-based applications and services associated with thosecloud-based content items.

In many cases, a cloud-based or cloud-backed content item cannot berepresented in file-based storage systems, and its content cannot berendered using other applications, such as traditional fileapplications, or may lose some cloud-backed features and functionalitieswhen rendered through an application other than the specific cloud-basedapplication associated with the cloud-based document. Disadvantageously,the increasing use of cloud-based and cloud-backed content items andapplications from different cloud-based services and the lacking orlimited support for such content items by a single storage solution havecreated an explosion of content items that are increasingly scatteredacross different systems and devices.

BRIEF DESCRIPTION OF THE DRAWINGS

The above-recited and other advantages and features of the presenttechnology will become apparent by reference to specific implementationsillustrated in the appended drawings. A person of ordinary skill in theart will understand that these drawings only show some examples of thepresent technology and would not limit the scope of the presenttechnology to these examples. Furthermore, the skilled artisan willappreciate the principles of the present technology as described andexplained with additional specificity and detail through the use of theaccompanying drawings in which:

FIG. 1A shows an example configuration of a computing environmentincluding a content management system and client devices;

FIG. 1B shows an example collaboration content management system;

FIG. 2 shows a schematic diagram of an example architecture forsynchronizing content between a content management system and clientdevices;

FIG. 3 shows an example architecture for integrating cloudfunctionalities and content from different cloud services into a contentmanagement system;

FIG. 4 is a Venn diagram showing functional similarities and differencesbetween various types of content items;

FIG. 5A shows an example functionality mapping between a cloud servicecontent item on a third-party cloud service and a smart pointer in acontent management system;

FIG. 5B shows an example functionality mapping between a cloud servicecontent item on a third-party cloud service and a canonical content itemin a content management system;

FIG. 5C shows an example functionality mapping between a cloud servicecontent item on a third-party cloud service and a basic pointer in acontent management system;

FIG. 6A shows an example user experience and use case of a smart pointerbeing accessed through a browser application on a client device and acloud service content item being accessed through a browser applicationon another client device;

FIG. 6B shows an example user experience and use case of a canonicalcontent item being accessed through a browser application on a clientdevice and a cloud service content item being accessed through a browserapplication on another client device;

FIG. 6C shows another example user experience and use case of a smartpointer being accessed through a client application on a client deviceand a cloud service content item being accessed through a browserapplication on another client device;

FIG. 6D shows another example user experience and use case of acanonical content item being accessed through a client application on aclient device and a cloud service content item being accessed through abrowser application on another client device;

FIG. 7A shows an example process for providing a smart pointerreferencing a cloud service content item, and providing a client deviceaccess to the content and functionalities of the cloud service contentitem through the smart pointer;

FIG. 7B shows an example process for providing a client device access tothe content and functionalities of a cloud service content item througha smart pointer and a client application on a client device;

FIG. 7C shows an example process for providing a canonical content itemassociated with a cloud service content item, and providing a clientdevice access to the content and functionalities of the cloud servicecontent item through the canonical content item;

FIG. 7D shows an example process for providing a client device access tothe content and functionalities of a cloud service content item througha canonical content item and client application on a client device;

FIG. 8 shows an example flow for exchanging content, metadata andupdates associated with a cloud service content item between a contentmanagement system and a third-party cloud service;

FIG. 9A shows an example flow for creating associations between contentand metadata in a cloud service content item on a third-party cloudservice and a smart pointer on a content management system;

FIG. 9B shows an example flow for creating associations between contentand metadata in a cloud service content item on a third-party cloudservice and a canonical content item on a content management system;

FIG. 10 shows an example flow for pushing local changes to a smartpointer and a canonical content item on a client device to a third-partycloud service hosting content items associated with the smart pointerand the canonical content item;

FIG. 11 shows an example link-based mechanism for sharing canonicalcontent items stored in a content management system with users anddevices;

FIG. 12 shows an example flow for routing users to live collaborationsessions;

FIG. 13A shows an example method for implementing smart pointers on acontent management system;

FIG. 13B shows an example method for implementing canonical contentitems on a content management system;

FIG. 13C shows an example method for implementing cloud-based contentitems, cloud-backed content items, and smart pointers on a contentmanagement system;

FIG. 13D shows an example method for implementing access control forcloud-based content items and cloud-backed content items on a contentmanagement system; and

FIG. 14 shows an example system for implementing various aspects of thepresent technology.

DETAILED DESCRIPTION

Various examples of the present technology are discussed in detailbelow. While specific implementations are discussed, it should beunderstood that this is done for illustration purposes only. A personskilled in the relevant art will recognize that other components andconfigurations may be used without parting from the spirit and scope ofthe present technology.

Cloud storage systems allow users to store and access content itemsacross multiple devices. The content items may include, but are notlimited to, files, documents, messages (e.g., email messages or textmessages), media files (e.g., photos, videos, and audio files), folders,or any other unit of content. Content items may be shared with multipleusers, edited, deleted, added, renamed, moved and/or otherwise accessedor manipulated. However, in many cases, a single cloud storage system orsolution may not be capable of representing, rendering, and/or managingcontent items, such as cloud-based and cloud-backed content items,created or supported by specific cloud-based applications hosted bydifferent cloud-based services or providers. As a result, users oftenstore and access such content items from different cloud storage andcontent systems, while maintaining and accessing other content items onseparate cloud storage systems.

Moreover, as previously explained, the increasing use of cloud-based orcloud-backed content items and applications from different cloud-basedservices and the lacking or limited support for such content items by asingle storage solution have created an explosion of content items thatare increasingly scattered across different systems and devices. Thescattered nature of a user's content can significantly hamper the user'sability to organize the content, gain uniform or complete access to thecontent and associated functionalities from a single cloud storagesystem, and collaborate with other users. These issues can quicklymultiply as users attempt to collaborate with more users and implement agrowing variety of cloud-based and cloud-backed content items andapplications, often causing content silos that are extremely difficultto manage.

The technologies herein can provide an integrated and unified solutionthat addresses or overcomes the foregoing and other technical problemsand limitations. For example, the technologies herein can provide acloud storage solution that is capable of organizing, representing andrendering cloud-based and cloud-backed documents from a wide variety ofcloud-based applications or services while maintaining support for thevarious cloud-based or cloud-backed functionalities associated with suchcloud-based and cloud-backed content items, such as content creationwithin the cloud-based or cloud-backed content items. In some cases, thecloud storage solution herein can also extend the functionalities orfeatures of such cloud-based and cloud-backed content items to includeadditional functionalities or features provided by the cloud storagesolution herein, such as sharing, organization, collaboration, andsecurity functionalities or features.

In some aspects, the disclosed technologies are deployed in the contextof a content management system, such as a cloud storage service, havingcontent item synchronization capabilities and collaboration features,among others. An example configuration 100 of a content managementsystem and environment is shown in FIG. 1A, which depicts contentmanagement system 110 interacting with client device 150.

Accounts

Content management system 110 can store content items in associationwith accounts, as well as perform a variety of content item managementtasks, such as retrieve, modify, browse, and/or share the contentitem(s). Furthermore, content management system 110 can enable anaccount to access content item(s) from multiple client devices.

Content management system 110 supports a plurality of accounts. Anentity (user, group of users, team, company, etc.) can create an accountwith content management system, and account details can be stored inaccount database 140. Account database 140 can store profile informationfor registered entities. In some cases, profile information forregistered entities includes a username and/or email address. Accountdatabase 140 can include account management information, such as accounttype (e.g. various tiers of free or paid accounts), storage spaceallocated, storage space used, client devices 150 having a registeredcontent management client application 152 resident thereon, securitysettings, personal configuration settings, etc.

Account database 140 can store groups of accounts associated with anentity. Groups can have permissions based on group policies and/oraccess control lists, and members of the groups can inherit thepermissions. For example, a marketing group can have access to one setof content items while an engineering group can have access to anotherset of content items. An administrator group can modify groups, modifyuser accounts, etc.

Content Item Storage

A feature of content management system 110 is the storage of contentitems, which can be stored in content storage 142. Content items can beany digital data such as documents, collaboration content items, textfiles, audio files, image files, video files, webpages, executablefiles, binary files, etc. A content item can also include collections orother mechanisms for grouping content items together with differentbehaviors, such as folders, zip files, playlists, albums, etc. Acollection can refer to a folder, or a plurality of content items thatare related or grouped by a common attribute. In some embodiments,content storage 142 is combined with other types of storage or databasesto handle specific functions. Content storage 142 can store contentitems, while metadata regarding the content items or objects associatedwith the content items or user accounts can be stored in metadata store146. Likewise, data regarding where a content item is stored in contentstorage 142 can be stored in content directory 144. Additionally, dataregarding changes, access, etc., can be stored in filesystem 148.

Each of the various storages/databases such as content storage 142,content directory 144, filesystem 148, and metadata store 146 can becomprised of more than one such storage or database and can bedistributed over many devices and locations. Other configurations arealso possible. For example, data from content storage 142, contentdirectory 144, filesystem 148, and/or metadata store 146 may be combinedinto one or more content storages or databases or further segmented intoadditional content storages or databases. Thus, content managementsystem 110 may include more or less storages and/or databases than shownin FIG. 1A.

In some embodiments, content storage 142 is associated with at least onecontent storage service 116, which includes software or other processorexecutable instructions for managing the storage of content itemsincluding, but not limited to, receiving content items for storage,preparing content items for storage, selecting a storage location forthe content item, retrieving content items from storage, etc. In someembodiments, content storage service 116 can divide a content item intosmaller chunks for storage at content storage 142. The location of eachchunk making up a content item can be recorded in content directory 144.Content directory 144 can include a content entry for each content itemstored in content storage 142. The content entry can be associated witha unique ID, which identifies a content item.

In some embodiments, the unique ID, which identifies a content item incontent directory 144, can be derived from a deterministic hashfunction. This method of deriving a unique ID for a content item canensure that content item duplicates are recognized as such since thedeterministic hash function will output the same identifier for everycopy of the same content item, but will output a different identifierfor a different content item. Using this methodology, content storageservice 116 can output a unique ID for each content item.

Content storage service 116 can also designate or record a content pathfor a content item in metadata store 146. The content path can includethe name of the content item and/or folder hierarchy associated with thecontent item. For example, the content path can include a folder or pathof folders in which the content item is stored in a local file system ona client device. While content items are stored in content storage 142in blocks and may not be stored under a tree like directory structure,such directory structure is a comfortable navigation structure forusers. Content storage service 116 can define or record a content pathfor a content item wherein the “root” node of a directory structure canbe a namespace for each account. Within the namespace can be a directorystructure defined by a user of an account and/or content storage service116. Metadata store 146 can store the content path for each content itemas part of a content entry.

In some embodiments the namespace can include additional namespacesnested in the directory structure as if they are stored within the rootnode. This can occur when an account has access to a shared collection.Shared collections can be assigned their own namespace within contentmanagement system 110. While some shared collections are actually a rootnode for the shared collection, they are located subordinate to theaccount namespace in the directory structure, and can appear as a folderwithin a folder for the account. As addressed above, the directorystructure is merely a comfortable navigation structure for users, butdoes not correlate to storage locations of content items in contentstorage 142.

While the directory structure in which an account views content itemsdoes not correlate to storage locations at content management system110, the directory structure can correlate to storage locations onclient device 150 depending on the file system used by client device150.

As addressed above, a content entry in content directory 144 can alsoinclude the location of each chunk making up a content item. Morespecifically, the content entry can include content pointers thatidentify the location in content storage 142 of the chunks that make upthe content item.

In addition to a content path and content pointer, a content entry incontent directory 144 can also include a user account identifier thatidentifies the user account that has access to the content item and/or agroup identifier that identifies a group with access to the content itemand/or a namespace to which the content entry belongs.

Content storage service 116 can decrease the amount of storage spacerequired by identifying duplicate content items or duplicate blocks thatmake up a content item or versions of a content item. Instead of storingmultiple copies, content storage 142 can store a single copy of thecontent item or block of the content item and content directory 144 caninclude a pointer or other mechanism to link the duplicates to thesingle copy.

Content storage service 116 can also store metadata describing contentitems, content item types, folders, file path, and/or the relationshipof content items to various accounts, collections, or groups in metadatastore 146, in association with the unique ID of the content item.

Content storage service 116 can also store a log of data regardingchanges, access, etc., in filesystem 148. Filesystem 148 can include theunique ID of the content item and a description of the change or accessaction along with a time stamp or version number and any other relevantdata. Filesystem 148 can also include pointers to blocks affected by thechange or content item access. Content storage service can provide theability to undo operations, by using a content item version control thattracks changes to content items, different versions of content items(including diverging version trees), and a change history that can beacquired from the filesystem 148.

Content Item Synchronization

Another feature of content management system 110 is synchronization ofcontent items with at least one client device 150. Client device(s) cantake different forms and have different capabilities. For example,client device 150 ₁ is a computing device having a local file systemaccessible by multiple applications resident thereon. Client device 150₂ is a computing device wherein content items are only accessible to aspecific application or by permission given by the specific application,and the content items are typically stored either in an applicationspecific space or in the cloud. Client device 150 ₃ is any client deviceaccessing content management system 110 via a web browser and accessingcontent items via a web interface. While example client devices 150 ₁,150 ₂, and 150 ₃ are depicted in form factors such as a laptop, mobiledevice, or web browser, it should be understood that the descriptionsthereof are not limited to devices of these example form factors. Forexample a mobile device such as client 150 ₂ might have a local filesystem accessible by multiple applications resident thereon, or client150 ₂ might access content management system 110 via a web browser. Assuch, the form factor should not be considered limiting when consideringclient 150's capabilities. One or more functions described herein withrespect to client device 150 may or may not be available on every clientdevice depending on the specific capabilities of the device—the fileaccess model being one such capability.

In many embodiments, client devices are associated with an account ofcontent management system 110, but in some embodiments client devicescan access content using shared links and do not require an account.

As noted above, some client devices can access content management system110 using a browser application 166, such as a web browser. For example,client device 150 can use browser application 166 to access web pagesand content on content management system 110. However, client devicescan also access content management system 110 using client application152 stored and running on client device 150. Client application 152 caninclude a client synchronization service 156. Client synchronizationservice 156 can be in communication with server synchronization service112 to synchronize changes to content items between client device 150and content management system 110.

Client device 150 can synchronize content with content management system110 via client synchronization service 156. The synchronization can beplatform agnostic. That is, content can be synchronized across multipleclient devices of varying type, capabilities, operating systems, etc.Client synchronization service 156 can synchronize any changes (new,deleted, modified, copied, or moved content items) to content items in adesignated location of a file system of client device 150.

Content items can be synchronized from client device 150 to contentmanagement system 110, and vice versa. In embodiments whereinsynchronization is from client device 150 to content management system110, a user can manipulate content items directly from the file systemof client device 150, while client synchronization service 156 canmonitor directory on client device 150 for changes to files within themonitored folders.

When client synchronization service 156 detects a write, move, copy, ordelete of content in a directory that it monitors, clientsynchronization service 156 can synchronize the changes to contentmanagement system service 116. In some embodiments, clientsynchronization service 156 can perform some functions of contentmanagement system service 116 including functions addressed above suchas dividing the content item into blocks, hashing the content item togenerate a unique identifier, etc. Client synchronization service 156can index content within client storage index 164 and save the result instorage index 164. Indexing can include storing paths plus a uniqueserver identifier, and a unique client identifier for each content item.In some embodiments, client synchronization service 156 learns theunique server identifier from server synchronization service 112, andlearns the unique client identifier from the operating system of clientdevice 150.

Client synchronization service 156 can use storage index 164 tofacilitate the synchronization of at least a portion of the contentwithin client storage with content associated with a user account oncontent management system 110. For example, client synchronizationservice 156 can compare storage index 164 with content management system110 and detect differences between content on client storage and contentassociated with a user account on content management system 110. Clientsynchronization service 156 can then attempt to reconcile differences byuploading, downloading, modifying, and deleting content on clientstorage as appropriate. Content storage service 116 can store thechanged or new block for the content item and update filesystem 148,metadata store 146, content directory 144, content storage 142, accountdatabase 140, etc. as appropriate.

When synchronizing from content management system 110 to client device150, a mount, modification, addition, deletion, move of a content itemrecorded in filesystem 148 can trigger a notification to be sent toclient device 150 using notification service 117. When client device 150is informed of the change a request changes listed in filesystem 148since the last synchronization point known to the client device. Whenclient device 150 determines that it is out of synchronization withcontent management system 110, client synchronization service 156requests content item blocks including the changes, and updates itslocal copy of the changed content items.

In some embodiments, storage index 164 stores tree data structureswherein one tree reflects the latest representation of a directoryaccording to server synchronization service 112, while another treereflects the latest representation of the directory according to clientsynchronization service 156. Client synchronization service can work toensure that the tree structures match by requesting data from serversynchronization service 112 or committing changes on client device 150to content management system 110.

Sometimes client device 150 might not have a network connectionavailable. In this scenario, client synchronization service 156 canmonitor the linked collection for content item changes and queue thosechanges for later synchronization to content management system 110 whena network connection is available. Similarly, a user can manually start,stop, pause, or resume synchronization with content management system110.

Client synchronization service 156 can synchronize all contentassociated with a particular user account on content management system110. Alternatively, client synchronization service 156 can selectivelysynchronize a portion of the content of the total content associatedwith the particular user account on content management system 110.Selectively synchronizing only a portion of the content can preservespace on client device 150 and save bandwidth.

In some embodiments, client synchronization service 156 selectivelystores a portion of the content associated with the particular useraccount and stores placeholder content items in client storage for theremainder portion of the content. For example, client synchronizationservice 156 can store a placeholder content item that has the samefilename, path, extension, metadata, of its respective complete contentitem on content management system 110, but lacking the data of thecomplete content item. The placeholder content item can be a few bytesor less in size while the respective complete content item might besignificantly larger. After client device 150 attempts to access thecontent item, client synchronization service 156 can retrieve the dataof the content item from content management system 110 and provide thecomplete content item to accessing client device 150. This approach canprovide significant space and bandwidth savings while still providingfull access to a user's content on content management system 110.

Collaboration Features

Another feature of content management system 110 is to facilitatecollaboration between users. Collaboration features include content itemsharing, commenting on content items, co-working on content items,instant messaging, providing presence and seen state informationregarding content items, etc.

Sharing

Content management system 110 can manage sharing content via sharingservice 128. Sharing content by providing a link to the content caninclude making the content item accessible from any computing device innetwork communication with content management system 110. However, insome embodiments a link can be associated with access restrictionsenforced by content management system 110 and access control list 145.Sharing content can also include linking content using sharing service128 to share content within content management system 110 with at leastone additional user account (in addition to the original user accountassociated with the content item) so that each user account has accessto the content item. The additional user account can gain access to thecontent by accepting the content, which will then be accessible througheither web interface service 124 or directly from within the directorystructure associated with their account on client device 150. Thesharing can be performed in a platform agnostic manner. That is, thecontent can be shared across multiple client devices 150 of varyingtype, capabilities, operating systems, etc. The content can also beshared across varying types of user accounts.

To share a content item within content management system 110 sharingservice 128 can add a user account identifier or multiple user accountidentifiers to a content entry in access control list database 145associated with the content item, thus granting the added user accountaccess to the content item. Sharing service 128 can also remove useraccount identifiers from a content entry to restrict a user account'saccess to the content item. Sharing service 128 can record content itemidentifiers, user account identifiers given access to a content item,and access levels in access control list database 145. For example, insome embodiments, user account identifiers associated with a singlecontent entry can specify different permissions for respective useraccount identifiers with respect to the associated content item.

To share content items outside of content management system 110, sharingservice 128 can generate a custom network address, such as a uniformresource locator (URL), which allows any web browser to access thecontent item or collection in content management system 110 without anyauthentication. To accomplish this, sharing service 128 can includecontent identification data in the generated URL, which can later beused to properly identify and return the requested content item. Forexample, sharing service 128 can include the account identifier and thecontent path or a content item identifying code in the generated URL.Upon selection of the URL, the content identification data included inthe URL can be transmitted to content management system 110, which canuse the received content identification data to identify the appropriatecontent item and return the content item.

In addition to generating the URL, sharing service 128 can also beconfigured to record in access control list database 145 that a URL tothe content item has been created. In some embodiments, the contententry associated with a content item can include a URL flag indicatingwhether a URL to the content item has been created. For example, the URLflag can be a Boolean value initially set to 0 or false to indicate thata URL to the content item has not been created. Sharing service 128 canchange the value of the flag to 1 or true after generating a URL to thecontent item.

In some embodiments, sharing service 128 can associate a set ofpermissions to a URL for a content item. For example, if a user attemptsto access the content item via the URL, sharing service 128 can providea limited set of permissions for the content item. Examples of limitedpermissions include restrictions that the user cannot download thecontent item, save the content item, copy the content item, modify thecontent item, etc. In some embodiments, limited permissions includerestrictions that only permit a content item to be accessed from with aspecified domain, i.e., from within a corporate network domain, or byaccounts associated with a specified domain, e.g., accounts associatedwith a company account (e.g., @acme.com).

In some embodiments, sharing service 128 can also be configured todeactivate a generated URL. For example, each content entry can alsoinclude a URL active flag indicating whether the content should bereturned in response to a request from the generated URL. For example,sharing service 128 can only return a content item requested by agenerated link if the URL active flag is set to 1 or true. Thus, accessto a content item for which a URL has been generated can be easilyrestricted by changing the value of the URL active flag. This allows auser to restrict access to the shared content item without having tomove the content item or delete the generated URL. Likewise, sharingservice 128 can reactivate the URL by again changing the value of theURL active flag to 1 or true. A user can thus easily restore access tothe content item without the need to generate a new URL.

In some embodiments, content management system 110 can designate a URLfor uploading a content item. For example, a first user with a useraccount can request such a URL, provide the URL to a contributing userand the contributing user can upload a content item to the first user'suser account using the URL.

Events

Content management system 110 can track, create, and store eventsinvolving content items and/or user activity. For example, when a userinteracts with a content item (e.g., add, edit, post, share, delete,comment, move, rename, etc.) and/or interacts with another user (e.g.,message, comment, collaborate, etc.), event service 136 can generate anevent for such interaction. When event service 136 detects a userinteraction with a content item and/or another user, event service 136can create an event identifier (e.g., unique event identifier) and eventtype, and associate the event identifier and event type with the user(e.g., user identifier and namespace identifier) to create an event orevent record for the interaction. After the event is created, eventservice 136 can send the event identifier and any information associatedwith the event to events store 143 for storage.

Events store 143 can include one or more storage systems, such as one ormore databases, for storing events and associated information. In someexamples, events store 143 can include a distributed database ordistributed storage system. Events store 143 can receive and store theevent data for access by content management system 110.

Team Service

In some embodiments content management system 110 includes team service130. Team service 130 can provide functionality for creating andmanaging defined teams of user accounts. Teams can be created for acompany, with sub-teams (e.g., business units, or project teams, etc.),and user accounts assigned to teams and sub-teams, or teams can becreated for any defined group of user accounts. Teams service 130 canprovide a common shared space for the team, private user accountfolders, and access limited shared folders. Teams service can alsoprovide a management interface for an administrator to managecollections and content items within team, and can manage user accountsthat are associated with the team.

Authorization Service

In some embodiments, content management system 110 includesauthorization service 132. Authorization service 132 ensures that a useraccount attempting to access a namespace has appropriate rights toaccess the namespace. Authorization service 132 can receive a token fromclient application 152 that follows a request to access a namespace andcan return the capabilities permitted to the user account. For useraccounts with multiple levels of access (e.g. a user account with userrights and administrator rights) authorization service 132 can alsorequire explicit privilege escalation to avoid unintentional actions byadministrators.

Presence and Seen State

In some embodiments, content management system can provide informationabout how users with which a content item is shared are interacting orhave interacted with the content item. In some embodiments, contentmanagement system 110 can report that a user with which a content itemis shared is currently viewing the content item. For example, clientcollaboration service 160 can notify notifications service 117 whenclient device 150 is accessing the content item. Notifications service117 can then notify all client devices of other users having access tothe same content item of the presence of the user of client device 150with respect to the content item. Content management system 110 (e.g.,via event service 136) and/or client device 150 can track userinteractions with content, such as read or write events, and maintain ahistory of such events and interactions for a user (e.g., events store143).

In some embodiments, content management system 110 can report a historyof user interaction with a shared content item. Collaboration service126 can query data sources such as events store 143, metadata store 146and filesystem 148 to determine that a user has saved the content item,that a user has yet to view the content item, etc., and disseminate thisstatus information using notification service 117 to other users so thatthey can know who currently is or has viewed or modified the contentitem.

Collaboration service 126 can facilitate comments associated withcontent, even if a content item does not natively support commentingfunctionality. Such comments can be stored in metadata store 146.

Collaboration service 126 can originate and transmit notifications forusers. For example, a user can mention another user in a comment andcollaboration service 126 can send a notification to that user that hehas been mentioned in the comment. Various other content item events cantrigger notifications, including deleting a content item, sharing acontent item, etc.

Collaboration service 126 can provide a messaging platform whereby userscan send and receive instant messages, voice calls, emails, etc.

Collaboration Content Items

In some embodiments content management service can also includeCollaborative document service 134 which can provide an interactivecontent item collaboration platform whereby users can simultaneouslycreate collaboration content items, comment in the collaboration contentitems, and manage tasks within the collaboration content items.Collaboration content items can be files that users can create and editusing a collaboration content item editor, and can contain collaborationcontent item elements. Collaboration content item elements may include acollaboration content item identifier, one or more author identifiers,collaboration content item text, collaboration content item attributes,interaction information, comments, sharing users, etc. Collaborationcontent item elements can be stored as database entities, which allowsfor searching and retrieving the collaboration content items. Multipleusers may access, view, edit, and collaborate on collaboration contentitems at the same time or at different times. In some embodiments thiscan be managed by requiring two users access a content item through aweb interface and there they can work on the same copy of the contentitem at the same time.

Collaboration Companion Interface

In some embodiments client collaboration service 160 can provide anative application companion interface for the purpose of displayinginformation relevant to a content item being presented on client device150. In embodiments wherein a content item is accessed by a nativeapplication stored and executed on client device 150, where the contentitem is in a designated location of the file system of client device 150such that the content item is managed by content application 152, thenative application may not provide any native way to display the aboveaddressed collaboration data. In such embodiments, client collaborationservice 160 can detect that a user has opened a content item, and canprovide an overlay with additional information for the content item,such as collaboration data. For example, the additional information caninclude comments for the content item, status of the content item,activity of other users previously or currently viewing the contentitem. Such an overlay can warn a user that changes might be lost becauseanother user is currently editing the content item.

In some embodiments, one or more of the services or storages/databasesdiscussed above can be accessed using public or private applicationprogramming interfaces.

Certain software applications can access content storage 142 via an APIon behalf of a user. For example, a software package such as anapplication running on client device 150, can programmatically make APIcalls directly to content management system 110 when a user providesauthentication credentials, to read, write, create, delete, share, orotherwise manipulate content.

A user can view or manipulate content stored in a user account via a webinterface generated and served by web interface service 124. Forexample, the user can navigate in a web browser to a web addressprovided by content management system 110. Changes or updates to contentin the content storage 142 made through the web interface, such asuploading a new version of a content item, can be propagated back toother client devices associated with the user account. For example,multiple client devices, each with their own client software, can beassociated with a single account and content items in the account can besynchronized between each of the multiple client devices.

Client device 150 can connect to content management system 110 on behalfof a user. A user can directly interact with client device 150, forexample when client device 150 is a desktop or laptop computer, phone,television, internet-of-things device, etc. Alternatively oradditionally, client device 150 can act on behalf of the user withoutthe user having physical access to client device 150, for example whenclient device 150 is a server.

Some features of client device 150 are enabled by an applicationinstalled on client device 150. In some embodiments, the application caninclude a content management system specific component. For example, thecontent management system specific component can be a stand-aloneapplication 152, one or more application plug-ins, and/or a browserextension. However, the user can also interact with content managementsystem 110 via a third-party application, such as a web browser, thatresides on client device 150 and is configured to communicate withcontent management system 110. In various implementations, theclient-side application 152 can present a user interface (UI) for a userto interact with content management system 110. For example, the usercan interact with the content management system 110 via a file systemexplorer integrated with the file system or via a webpage displayedusing a web browser application.

In some embodiments, client application 152 can be configured to manageand synchronize content for more than one account of content managementsystem 110. In such embodiments client application 152 can remain loggedinto multiple accounts and provide normal services for the multipleaccounts. In some embodiments, each account can appear as folder in afile system, and all content items within that folder can besynchronized with content management system 110. In some embodiments,client application 152 can include a selector to choose one of themultiple accounts to be the primary account or default account.

While content management system 110 is presented with specificcomponents, it should be understood by one skilled in the art, that thearchitectural configuration of system 100 is simply one possibleconfiguration and that other configurations with more or fewercomponents are possible. Further, a service can have more or lessfunctionality, even including functionality described as being withanother service. Moreover, features described herein with respect to anembodiment can be combined with features described with respect toanother embodiment.

While configuration 100 is presented with specific components, it shouldbe understood by one skilled in the art, that the architecturalconfiguration of system 100 is simply one possible configuration andthat other configurations with more or fewer components are possible.

FIG. 1B shows an example collaboration content management system 170,according to some examples. Collaboration content management system 170can include one or more servers and/or applications for hosting andrunning collaboration service 126. Collaboration content managementsystem 170 can be part of content management system 110 or separate fromcontent management system 110. For clarity and explanation purposes,collaboration content management system 170 will be described herein aspart of content management system 110.

Collaboration service 126 can include one or more components and/orservices. For example, collaboration service 126 may includeproductivity management service 180, collaboration content itemprocessing interface service 182, collaboration content item editor 184,user notification service 186, collaboration content item presentationservice 188, and productivity management modification service 190.Productivity management service 180, collaboration content itemprocessing interface service 182, collaboration content item editor 184,user notification service 186, collaboration content item presentationservice 188, and/or productivity management modification service 190 caninclude one or more services, components, devices, etc., such asphysical servers, virtual machines, software containers, etc. Moreover,one or more of productivity management service 180, collaborationcontent item processing interface service 182, collaboration contentitem editor 184, user notification service 186, collaboration contentitem presentation service 188, and productivity management modificationservice 190 may be coupled to one another or to components notexplicitly shown.

Productivity management service 180 may be configured to gatherproductivity data from content management system 110. In variousembodiments, productivity management service 180 identifies an event andgathers information related to the event. For instance, productivitymanagement service 180 may gather a specific calendar entry and/or aspecific task from an online calendar. Productivity management service180 may further gather information from the calendar entry or gatherinformation related to the calendar entry such as time(s), date(s),relevant locations, title(s), agenda(s), summaries, description(s),and/or attendees related to the event. Productivity management service180 may provide the productivity data to the other modules ofcollaboration service 126.

Collaboration content item processing interface service 182 may beconfigured to interface with collaboration service 126. In variousembodiments, collaboration content item processing interface service 182may provide collaboration content items to one or more modules ofcollaboration service 126, as described further herein.

Collaboration content item editor 184 may be configured to create and/ormodify collaboration content items. A collaboration content item may becreated in a variety of ways. In some embodiments, collaboration contentitem editor 184 enables creation of the collaboration content item intothe content management system 106. Collaboration content item editor 184may enable access to or be any collaboration content item editingapplication (e.g., Microsoft Word®, Google Docs®, or the like) either inthe cloud or executed locally. In one example, content management system106 may provide to one of client devices 150 a user interface element(e.g., a box or a button) that allows creation of a new collaborationcontent item.

In some embodiments, collaboration content item editor 184 may createthe collaboration content item in conjunction with the productivitymanagement service 180. For example, collaboration content item editor184 may provide a suggestion to a user to create or invoke acollaboration content item associated with an upcoming event. In variousembodiments, collaboration service 126 may identify a user that isopening or otherwise using collaboration content item editor 184.Productivity management service 180 may identify an upcoming event forthe user on the user's calendar. Subsequently, collaboration contentitem editor 184 may provide a suggestion to the user to create or invokethe collaboration content item associated with the upcoming event.

Although it is discussed that collaboration content item editor 184 mayprovide a suggestion to the user to create or invoke the collaborationcontent item associated with the upcoming event, it will be appreciatedthat the suggestion to create or invoke the collaboration content itemmay be made by any application. For example, a user may log into and/orotherwise access any application or suite of applications. Once the useris identified and an upcoming event is identified on the user'scalendar, any application may provide the user with the suggestion tocreate or invoke the collaboration content item associated with theupcoming event. The suggestion may be provided to the user in any numberof ways. In one example, an application suite management system (e.g.,managing a variety of different applications) may provide the suggestionin a notification section of a window. In another example, a workspacemay include the suggestion to the user in a section dedicated tonotifications. In a further example, an email program may generate anemail containing the suggestion to the user.

If the user requests creation or invocation of the collaboration contentitem in response to the suggestion, collaboration content item editor184 may create or invoke the requested collaboration content item. Ifthe application that provided the suggestion to the user is not acollaboration content item editor, then a collaboration content itemeditor may be executed and the requested collaboration content itemcreated and/or invoked in response to the user's request.

In accordance with some embodiments, collaboration content item editor184 may configure the productivity management service 180 to provideaccess to the collaboration content item (e.g., using a link, includingthe collaboration content item, or any other mechanism to enable accessto the collaboration content item) in a meeting request, a task entry,or the like. In some embodiments, collaboration content item editor 184may instruct productivity management service 180 to place an iconcorresponding to a link to the collaboration content item in thecalendar entry, meeting request, task entry, or the like. When a userhas opened the link (e.g., by clicking the icon), the user may bedirectly guided to the collaboration content item from the meetingrequest, task entry, or the like. In one example, the link in thecalendar entry may provide the user (e.g., using client device 150)access to a collaboration content item stored in content managementsystem 106 (e.g., in storage accessible through the cloud) or inproductivity management service 180.

Once the user requests to create or invoke the collaboration contentitem, collaboration content item editor 184 may create and/or invoke acollaboration content item. The collaboration content item may besubsequently edited, altered, viewed, changed, stored, and/or the likeby an editing application (e.g., either stored locally on a clientdevice or in the cloud). In various embodiments, one or more differentclient devices 150 may utilize different editing applications to makechanges to the collaboration content item. Collaboration content itemeditor 184 and/or other editing applications may allow for thecollaboration content item to be changed by multiple different usersusing different client devices 150 at the same time or substantially atthe same time (e.g., in real time or substantially in real time).

It will be appreciated that users may be automatically guided to acollaboration content item related to a calendar entry, meeting request,a task entry, or the like without human intervention. In someembodiments, users may be guided to a collaboration content item relatedto a calendar entry, a meeting request, a task entry, or the likewithout having the users separately open collaboration content itemediting applications. Such functionalities may prove particularlyconvenient for users seeking to take, review, or collaborate on notesassociated with an event, as these users need not open applicationsother than productivity management applications.

Collaboration content item editor 184 may receive from users additionalcontent for the collaboration content item. For example, collaborationcontent item editor 184 may be configured to receive from client devices150 changes or edits to the collaboration content item. In variousembodiments, the changes may include text, characters strings, or thelike. The changes may also include annotations to the collaborationcontent item, comments to the collaboration content item, files to beattached to the collaboration content item, pictures to be attached tothe collaboration content item, links to be attached to thecollaboration content item, tasks related to the collaboration contentitem, or the like that can be incorporated into the collaborationcontent item. In various embodiments, edits to the collaboration contentitem are collaboration. For instance, collaboration content item editor184 may obtain edits (e.g., text changes and/or additions of audiofiles, pictures, tables, or the like) from any number of client devices150 at a given time (or in real time). Collaboration edits may beincorporated in a variety of formats, including formats that providedifferent text attributes such as colors, fonts, styles, or the like fordifferent users.

In various embodiments, collaboration content item editor 184 (and or asecurity or permissions module associated with a server) may establishpermissions and/or security for the collaboration content item. Forexample, collaboration content item editor 184 may enable eventattendees to view and/or make edits to the collaboration content itemwhile others may not have rights to view the collaboration content itemsand/or make changes. Permissions and/or security may be enforced in anynumber of ways. However, access to the collaboration content item may,in various embodiments, be provided to attendees of the event or asubset of attendees.

In some implementations, users can enter commands by providingpre-established primitives. A primitive can be a specified sequence ofone or more characters that the content management system 106 recognizesas mapped to particular functionality. In some implementations, aprimitive can be followed by one or more parameters specifying how thesystem should implement the corresponding functionality. Examples ofprimitives include a user identification primitive (e.g., “@” followedby a username parameter—referred to herein as a mention of a user), atask creation primitive (e.g., “[ ]” followed by a task titleparameter), an emoji selector primitive (e.g., “:”), a content itemselector and reference insertion primitive (e.g., “+” followed by atcontentltem title parameter), a bullet list primitive (e.g., “*”), etc.Primitive parameters can define the corresponding functionality invarious ways.

For example, the +primitive can operate by taking the content specifiedby a contentItemTitle parameter and attempting to match it to anexisting content item. In some implementations, when such a match isfound, the primitive, and any associated parameter, can be replaced inthe collaboration content item with a reference to the content item,such as a URL. Such a reference, when activated, can load the referencedcollaboration content item. In some implementations, a primitive cantake another primitive as a parameter. For example, the content “[ ]@Jane” can be interpreted such that @Jane links to a user with theusername “Jane,” and this link is used by the primitive “[ ]” to createsa new task, where that task is assigned to the user Jane.

In various embodiments, collaborative content item editor 184 (and or asecurity or permissions module associated with a server) may establishpermissions and/or security for the collaborative content item. Forexample, collaborative content item editor 184 may enable eventattendees to view and/or make edits to the collaborative content itemwhile others may not have rights to view the collaborative content itemsand/or make changes. Permissions and/or security may be enforced in anynumber of ways. However, access to the collaborative content item may,in various embodiments, be provided to attendees of the event or asubset of attendees.

In various embodiments, access to the collaboration content item islimited based on storage access rights. For example, a user with accessrights to cloud storage may access, view, and/or make changes to thecollaboration content item. In some embodiments, a user with accessrights assigned by the content management system 106 may access, view,and/or make changes to the collaboration content item.

User notification service 186 may be configured to notify users of eachof client devices 150 of information related to the state and/orcontents of the collaboration content item. Notifications may be sent,for example as an email notification, a chat message notification, anotification in a display of the collaboration content item, or inrelation to the collaboration content item through a file system orother organizational system. In various embodiments, user notificationservice 186 provides notifications about changes to client devices 150.For example, user notification service 186 may notify users whether acollaboration content item has been created for an event. As anotherexample, user notification service 186 may notify specific users thatthey have been invited to attend an event.

Collaboration content item presentation service 188 may provide toclient devices 150 selected collaboration content items. Thecollaboration content items may be displayed in client devices 150through a native application, an Internet browsing window, or the likesupported by client devices 150.

It will be appreciated that collaboration content item presentationservice 188 may restrict writing permissions to the collaborationcontent items at any time. In an example, prior to occurrence of theevent, collaboration content item presentation service 188 may restrictwriting permissions to the collaboration content item (and turn thecollaboration content item into a read-only collaboration content item)for all users except the creator or invoker of the collaboration contentitem. In some embodiments, the creator or invoker of the collaborationcontent item may select a subset of recipients to receive writingpermissions.

Collaboration content item presentation service 188 may also support acollaboration content item viewing portal users can use to view existingcollaboration content items. The collaboration content item viewingportal may order specific collaboration content items based on one ormore ordering factors. “Ordering factors,” as used herein, may includeany factors used to order collaboration content items. Ordering factorscan include factors used to order collaboration content itemschronologically. More specifically, in some embodiments, thecollaboration content item viewing portal orders collaboration contentitems according to the date(s) and/or times the collaboration contentitems were created. The collaboration content item viewing portal mayalso order collaboration content items according to the date(s) and/ortime(s) the collaboration content items were edited. In variousembodiments, the collaboration content item viewing portal orderscollaboration content items according to the date(s) and/or time(s) ofcorresponding events to which the collaboration content items wererelated. Ordering factors can also include factors used to ordercollaboration content items according to the preferences of a specificuser, such as whether the user has accepted events to which thecollaboration content items were related.

In some embodiments, a collaboration content item viewing portal may bededicated to a particular user who has received access to thecollaboration content item because the particular user was related to anevent. The user's collaboration content item viewing portal may provideaccess to any number of collaboration content items including thecollaboration content item. The collaboration content items representedin the collaboration content item viewing portal may be ordered in anynumber of ways. For example, the collaboration content item viewingportal may order collaboration content items based on date and time ofcorresponding events.

The collaboration content item viewing portal may support searchfunctions. For instance, the collaboration content item viewing portalmay enable or allow searching for collaboration content items accordingto textual strings, titles, event attendees, and/or other attributes.The search functions may allow a specific user to search one or morecollaboration content items for that user or for other users.

In some embodiments, productivity management modification service 190may be configured to coordinate collaboration content items withcalendar entries and to enable access to the collaboration content itemthrough calendar entries.

FIG. 2 shows a schematic diagram of an example architecture forsynchronizing content between content management system 110 and clientdevice 150 in configuration 100. In this example, client device 150interacts with content storage 142 and filesystem 148 respectively viacontent storage interface 206 and filesystem interface 202. Contentstorage interface 206 can be provided or managed by content storageservice 116, and filesystem interface 202 can be provided or managed byserver synchronization service 112. For example, content storageinterface 206 can be a subcomponent or subservice of content storageservice 116, and filesystem interface 202 can be a subcomponent orsubservice of server synchronization service 112.

Content storage interface 206 can manage communications, such as contentrequests or interactions, between client device 150 and content storage142. Content storage interface 206 can process requests from clientdevice 150 to upload and download content to and from content storage142. Content storage interface 206 can receive content requests (e.g.,downloads, uploads, etc.) from client device 150, authenticate clientdevice 150 via authentication service 212, communicate withauthorization service 132 to determine if client device 150 (and/or therequest from client device 150) is authorized to upload or download thecontent to or from content storage 142 (e.g., based on permissions inaccess control list 145), and interact with content storage 142 todownload or upload the content associated with the content requests fromclient device 150. If the request from client device 150 is a request todownload a content item, content storage interface 206 can retrieve thecontent item from content storage 142 and provide the content item toclient device 150. If the request from client device 150 is a request toupload a content item, content storage interface 206 can obtain thecontent item from client device 150 and upload the content item tocontent storage 142 for storage.

When processing content requests from client device 150, content storageinterface 206 can communicate with storage index 210 to check theavailability and/or storage location of the requested content in contentstorage 142, and track content items in content storage 142. Storageindex 210 can maintain an index of content items on content storage 142,which identifies the content items on content storage 142 and can alsoidentify a respective location of the content items within contentstorage 142. Thus, storage index 210 can track content items on contentstorage 142 as well as storage locations of the content items. Storageindex 210 can track entire content items, such as files, and/or portionsof the content items, such as blocks or chunks. In some cases, contentitems can be split into blocks or chunks, which can be stored at contentstorage 142 and tracked in storage index 210. For example, contentstorage 142 can store a content item as blocks or chunks of data thatinclude respective data portions of the content item. Storage index 210can track the blocks or chunks of the content item stored in contentstorage 142.

Filesystem interface 202 can manage communications, such as metadatarequests and content synchronizations and operations, between clientdevice 150 and filesystem 148. For example, filesystem interface 202 cantranslate, validate, authenticate, and/or process operations,configurations, and state information between client device 150 andfilesystem 148. Filesystem interface 202 can verify permissions from anFSAuth token in a cursor or through authorization service 132 toauthorize, or verify authorization of, requests sent by client device150 to filesystem 148. When processing requests or operations fromclient device 150, filesystem interface 202 can access namespacemembership store 208 to determine or verify namespace ownershipinformation for any namespaces associated with the requests oroperations from client device 150, and verify permissions of contentassociated with the requests or operations from client device 150.

Translation service 204 in filesystem interface 202 can performlinearization and translation operations for communications betweenclient device 150 and filesystem 148. For example, translation service204 can translate communications from client device 150 to a differentformat consistent with the structure and format of data in filesystem148, and vice versa. To illustrate, in some cases, client device 150 canprocess content item information (e.g., state, changes, versions, etc.)at client device 150 as operations, while filesystem 148 can process thesame information as content item revisions reflected by rows in a datastructure such as a database table. To enable synchronization of contentitem information between client device 150 and filesystem 148,translation service 204 can translate operations from client device 150into revisions suitable for filesystem 148, and can translate revisionsreflected in rows of data on filesystem 148 to operations suitable forclient device 150.

In some cases, content management system 110 (e.g., filesystem interface202, authorization service 132, or content storage interface 206) cangenerate a token that verifies or indicates that client device 150 isauthorized to access, update, download, or upload a requested contentitem. The token can include a device identifier associated with clientdevice 150, an account identifier associated with a user accountauthenticated or authorized at client device 150, a session identifierassociated with an authorized session at client device 150, a viewcontext, an encryption key, access permissions to identified contentitem(s), etc. The token can be provided with or in a cryptographicallysigned data object called a cursor, which will be described in greaterdetail below. Content management system 110 (e.g., filesystem interface202, authorization service 132, or content storage interface 206) cansend the token(s) to client device 150, and client device 150 canprovide the token to content management system 110 when requestingcontent item revisions and/or updates to filesystem 148 as furtherdescribed below. Client device 150 can also provide the token to contentstorage interface 206 to validate any content requests (e.g., downloads,uploads, etc.). Content storage interface 206 can use the token toauthorize queries to storage index 210 and upload or download contentitems to or from content storage 142.

For example, client device 150 can send to content storage interface 206a request to upload a content item to content storage 142. The requestcan include the token and the content item to be uploaded. Contentstorage interface 206 can use the token to authorize a query to storageindex 210 to check if the content item already exists on content storage142, and/or authorize the upload of the content item to content storage142. Client device 150 can provide the token to filesystem interface 202to authorize a request to store metadata on filesystem 148 to track theupload and revision of the content item.

FIG. 3 shows example architecture 300 for integrating data andfunctionalities of content items stored on or supported by differentcloud services with smart pointers, basic pointers, and/or canonicalcontent items stored on content management system 110. In this example,the different cloud services include third-party cloud services 302,304, 306 and collaboration content management system 170. Contentmanagement system 110 can store and manage smart pointers, basicpointers, canonical content items associated with cloud-based and/orcloud-backed content items, and receive associated content and/or cloudfunctionalities from third-party cloud services 302, 304, 306, andcollaboration content management system 170.

In some cases, third-party cloud services 302, 304, 306 andcollaboration content management system 170 can store and managecloud-based content items, cloud-backed content items, and/or thecontent or content items associated with smart pointers, basic pointersand/or canonical content items on content management system 110; and canprovide respective content, functionalities and/or features (e.g.,commenting, collaboration, sharing, editing, etc.) for representationsor instances (e.g., canonical content items, smart pointers, basicpointers) stored on content management system 110 and corresponding tospecific cloud-based and/or cloud-backed content items. For example,content management system 110 can store a basic pointer referencing acontent item (e.g., a cloud-based or cloud-backed content item) on athird-party cloud service (e.g., 302, 304, 306, 170), and obtain accessto the content and/or functionalities associated with the content itemreferenced by the basic pointer through the third-party cloud service.In another example, content management system 110 can store a smartpointer or a representation (e.g., a canonical representation) of acontent item (e.g., a cloud-based or cloud-backed content item) on athird-party cloud service (e.g., 302, 304, 306, 170), and use the smartpointer or the representation of the content item to access the contentitem and its associated content and functionalities from the third-partycloud service.

As further described herein, a basic pointer can be a representation ofa content item on a third-party cloud service (e.g., 302, 304, 306,170), that does not include the contents of the content item but insteadincludes a pointer or address (e.g., URL, URI, etc.) to the content itemon the third-party cloud service. The pointer or address can direct auser or device to the content item on the third-party cloud service toaccess the content item on the third-party cloud service. For example,in some cases, the basic pointer can be a light wrapper around anaddress, such as a URL, for accessing the content item on thethird-party cloud service. Thus, a basic pointer stored on contentmanagement system 110 can allow a user to access the associated contentitem on the third-party cloud service through the basic pointer oncontent management system 110.

On the other hand, as further described with reference to FIG. 5A, asmart pointer can be a representation of a content item on a third-partycloud service (e.g., 302, 304, 306, 170), that does not include thecontents of the content item but can render such contents and provideits associated functionalities. A smart pointer may appear to a user asanother content item stored in content management system 110, but maynot include the actual content of the third-party cloud service contentitem associated with the smart pointer. Instead, the smart pointer mayreference the third-party cloud service content item and provide accessto the actual content of the third-party cloud service content item fromthe smart pointer on content management system 110.

In some cases, in addition to providing access to the content of theassociated third-party cloud service content item, a smart pointer canprovide access to cloud functionalities provided by a third-party cloudservice and/or enable other functionalities supported by contentmanagement system 110, such as previews, searching, commenting, etc. Forexample, a smart pointer can reference a content item on a third-partycloud service and render the content item and provide associated cloudfunctionalities by obtaining the content and associated functionalitiesfrom the third-party cloud service. To illustrate, when a user opens oractivates the smart pointer, the user's client device can obtain fromthe third-party cloud service the contents and associatedfunctionalities of the content item referenced by the smart pointer. Theuser's client device can then render a view or instance of the contentitem, including its contents, and enable the functionalities obtainedfrom the third-party cloud service. Thus, the smart pointer can providea user experience similar to (or the same as) the user accessing thecontent item directly from the third-party cloud service, even thoughthe smart pointer and content management system 110 may not store theactual content of the content item.

Smart pointers can also provide organization and/or access primitivesassociated with content management system 110, while allowingthird-party cloud services storing the content items associated with thesmart pointers to continue to provide their own organization and/oraccess models in addition to those associated with content managementsystem 110. Thus, smart pointers can receive features and/orfunctionalities from third-party cloud services as well as contentmanagement system 110.

A canonical content item can be an instance or representation of acloud-based content item or a cloud-backed content item stored oncontent management system 110. In some cases, the canonical content itemcan include the actual content of the cloud-based or cloud-backedcontent item associated with the canonical content item, and can rendersuch content and provide associated functionalities, includingassociated cloud functionalities provided by third-party cloud services302, 304, 306, 170 and/or functionalities provided by content managementsystem 110.

A cloud-based content item can include a content item that isinextricably reliant on, and/or natively supported by, a cloud-basedapplication, editor, and/or service. The authoritative source of thecontent of the cloud-based content item can be the cloud-based contentmanagement system associated with the cloud-based content item.Cloud-based content items can include content items created, accessed,and/or manipulated via respective cloud-based applications or editors.Non-limiting examples of cloud-based content items can include DROPBOXPAPER, GOOGLE DOCS, QUIP, PREZI, etc.

A cloud-backed content item can include a content item capable ofintegrating and/or interacting with a cloud service and obtainingadditional functionality, such as real-time collaboration, from thecloud service. For example, a cloud-backed content item can be accessedthrough an application or editor, such as an online editor, that caninterface with a cloud service to obtain additional functionality forthe cloud-backed content item from the cloud service. Non-limitingexamples of cloud-backed content items include MICROSOFT WORD, MICROSOFTEXCEL, KEYNOTE and PAGES from APPLE IWORK, etc.

With reference to FIG. 4, Venn diagram 400 shows functional similaritiesand differences between various types of content items. In this example,circle 402 represents a set of cloud-based functionalities supported byone or more cloud services. Example cloud-based functionalities caninclude online access and storage functionalities as well ascollaboration functionalities such as collaborative editing, livecommenting, activity notifications, versioning, editing attribution,messaging, etc.

Circle 404 represents traditional content items (e.g., plain text files,image files, productivity documents, etc.), which can provide respectivecontent and functionalities irrespective or independent of any cloudservice. As illustrated by region 406 representing cloud-backed contentitems, some traditional content items can be cloud-backed files;meaning, such content items can obtain at least some of the cloud-basedfunctionalities represented by circle 402 from one or more cloudservices. The cloud-backed content items represented by region 406 canreceive such additional functionalities from applications or editorscapable of operating on the cloud-backed content items and interfacingwith one or more cloud services.

Like traditional content items, cloud-backed content items can becreated, accessed, and modified locally from a client device. In somecases, like traditional content items, cloud-backed content items cansupport filesystem operations, such as read, write, delete, rename,move, etc. Moreover, in some cases, cloud-backed content items can alsobe created, accessed, and modified from a web browser or online editor.

Circle 408 represents cloud-based content items. The cloud-based contentitems can support cloud-based functionalities (e.g., 402) and can derivesuch functionalities from one or more cloud services. The cloud-basedcontent items are inextricably reliant on one or more cloud services andnatively supported by an associated cloud-based application or editorfrom one or more associated cloud services. For example, a cloud-basedcontent item can be accessed from a cloud service through an onlineeditor provided by the cloud service. The online editor can be used tomanipulate the content in the cloud-based content item, collaborate withusers having access to the cloud-based content item, and derive anyother cloud-based functionalities from the cloud service associated withthe online editor.

Region 412 represents other cloud-based functionalities supported bycloud-based content items. In some examples, the other cloud-basedfunctionalities represented by region 412 can include one or morecloud-based functionalities that are not supported or available tocloud-backed content items and/or traditional content items. In otherexamples, the other cloud-based functionalities represented by region412 can include one or more functionalities that are supported bycloud-backed content items and traditional content items irrespective orindependent of any cloud service. In yet other examples, the othercloud-based functionalities represented by region 412 can includenon-collaborative functionalities.

Unlike traditional content items and cloud-backed content items,cloud-based content items are not native to non-cloud based applicationsor editors. Moreover, in some cases, unlike traditional content itemsand cloud-backed content items, cloud-based content items may notsupport filesystem operations or operate irrespective of a cloud-basedservice, application, and/or editor.

Returning to FIG. 3, third-party cloud services 302, 304, 306 andcollaboration content management system 170 can host and/or provide oneor more respective cloud-based applications or content item editors forusers to create, access, and/or interact with one or more respectivetypes of cloud-based or cloud-backed content items. In some cases,third-party cloud services 302, 304, 306 and collaboration contentmanagement system 170 can provide one or more types of cloud-basedapplications or editors respectively designed for one or more specifictypes of cloud-based or cloud-backed content items. For example, aparticular cloud-based application or editor can be designed to handle aspecific type of cloud-based content item, such as content creation,rendering, modification and other types of interactions with thecloud-based content item, as well as other features or functionalitiesfor the cloud-based content item such as collaboration, commenting,sharing, publishing, etc.

The cloud-based applications or editors can allow users to create ormodify online or web-based content items, publish the online orweb-based content items, share the online or web-based content items,collaborate with other users through the online or web-based contentitems, store the online or web-based content items on a cloud storageassociated with one or more respective cloud services, and/or interactin other ways with the online or web-based content items and/or usershaving access to the online or web-based content items. In some cases,the cloud-based applications or editors can allow users to create ormodify cloud-backed content items, publish the cloud-backed contentitems, share the cloud-backed content items, collaborate with otherusers through the cloud-backed content items, store the cloud-backedcontent items, and/or interact in other ways with the cloud-backedcontent items and/or users having access to the cloud-backed contentitems.

In some examples, the cloud-based applications or editors can beweb-based applications provided by the cloud services (e.g., 302, 304,306, 170) for creating and interacting with respective types ofcloud-based and/or cloud-backed content items. The cloud-basedapplications or editors can support various respective types of contentitems, content formats, content features, content functionalities, etc.In some cases, a particular type of cloud-based content item (e.g., 408)and/or associated functionalities may only be supported (fully orpartially) by a cloud-based application or editor associated with thatparticular type of cloud-based content item. In other cases, aparticular type of cloud-based content item and/or associatedfunctionalities may be supported by other software applications oreditors.

In some examples, a particular type of cloud-backed content item and/orassociated functionalities can be supported (fully or partially) by oneor more cloud-based applications or editors and/or other softwareapplications. For example, a particular type of cloud-backed contentitem may be supported by one or more software applications or tools on aclient device and may also be supported by a cloud-based application oreditor.

To illustrate, a cloud-backed content item may be supported by asoftware application or tool that is capable of rendering thecloud-backed content item without the use of a cloud-based applicationor editor. The software application or tool can allow a user to accessand interact with the cloud-backed content item from the user's device.The software application or tool can enable filesystem operations on thecloud-backed content item, such as read, write, delete, rename, move,and/or any other operations. The software application or tool maysupport a set of features or functionalities for that cloud-backedcontent item, but a cloud-based application or editor associated with acloud service can be used to access or enable additional, cloud-basedfunctionalities for that cloud-backed content item.

For example, in some cases, a cloud-based application or editor canprovide support for the cloud-backed content item, and can be used toaccess and interact with the cloud-backed content item. The cloud-basedapplication or editor can provide additional functionalities (e.g., inaddition to the functionalities supported by a native and/or non-cloudbased application or editor) to the cloud-backed content item, such aslive, collaborative editing; live commenting; messaging; and/or othercollaboration features.

Third-party cloud services 302, 304, 306 and collaboration contentmanagement system 170 can communicate with cloud integration service 320via interfaces 310, 312, 314, to receive or provide data and/or metadataassociated with one or more cloud-based and cloud-backed content items.Interfaces 310, 312, 314 can be, for example, application programminginterfaces (APIs) for exchanging data between cloud integration service320 and third-party cloud services 302, 304, 306 and collaborationcontent management system 170. Cloud integration service 320 can be aservice that implements the logic and/or functionalities for interactingwith cloud services (e.g., 302, 304, 306, 170) and/or content items onor supported by the cloud services (e.g., 302, 304, 306, 170), such ascloud-based or cloud-backed content items. In some examples, cloudintegration service 320 can communicate with cloud services (e.g., 302,304, 306, 170) to receive data and/or cloud functionalities, such ascloud-based collaboration functionalities, for content items stored oncontent management system 110, such as canonical content items.

For example, cloud integration service 320 can provide the functionalityfor communicating with the cloud services (e.g., 302, 304, 306, 170) toretrieve from the cloud services (e.g., 302, 304, 306, 170) metadataassociated with canonical content items (e.g., cloud-based contentitems, cloud-backed content items, etc.) or smart pointers on contentmanagement system 110; updating metadata associated with canonicalcontent items (e.g., cloud-based content items, cloud-backed contentitems, etc.) or smart pointers on content management system 110 based onmetadata updates received from the cloud services (e.g., 302, 304, 306,170); communicating with the cloud services (e.g., 302, 304, 306, 170)to retrieve and update content associated with canonical content items(e.g., cloud-based content items, cloud-backed content items, etc.) orsmart pointers on the content management system 110; sending to thecloud services (e.g., 302, 304, 306, 170) content and/or metadataassociated with content items (e.g., cloud-based or cloud-backed contentitems) maintained by the cloud services; exchanging with the cloudservices (e.g., 302, 304, 306, 170) activity information associated withcanonical content items (e.g., cloud-based or cloud-backed contentitems) or smart pointers; authenticating with the cloud services (e.g.,302, 304, 306, 170); providing tokens or authentication information tothe cloud services (e.g., 302, 304, 306, 170) for allowing the cloudservices to authenticate with content management system 110; etc.

Moreover, cloud integration service 320 can support various operationsfor communicating with the cloud services (e.g., 302, 304, 306, 170);accessing features and functionalities associated with canonical contentitems (e.g., cloud-based or cloud-backed content items) or smartpointers; accessing features and functionalities associated with contentmanagement system 110; interacting with canonical content items (e.g.,cloud-based content items or cloud-backed content items), smartpointers, or basic pointers stored in content storage 142 and/or clientdevice 150; interacting with content items (e.g., cloud-based orcloud-backed content items) on the cloud services (e.g., 302, 304, 306,170); interacting with the cloud services (e.g., 302, 304, 306, 170) toreceive or provide data and/or functionalities associated withcloud-based content items or cloud-backed content items stored on thecloud services (e.g., 302, 304, 306, 170) and/or canonical content items(e.g., cloud-based content items or cloud-backed content items), smartpointers, and/or basic pointers stored in content storage 142 or clientdevice 150; etc.

Non-limiting examples of operations supported by cloud integrationservice 320 include operations to create content items (e.g., canonicalcontent items such as cloud-based content items or cloud-backed contentitems, smart pointers, basic pointers, etc.) and/or associated data orcontent; operations to authenticate with cloud services (e.g., 302, 304,306, 170); operations to receive or update metadata associated withcontent items (e.g., cloud-based or cloud-backed content items) storedon or supported by one or more cloud services (e.g., 302, 304, 306,170); operations to retrieve content items (e.g., canonical contentitems such as cloud-based or cloud-backed content items, third-partycloud service content items associated with canonical content items)and/or related data from content storage 142, client device 150 and/orthe cloud services (e.g., 302, 304, 306, 170); operations to restorecontent items (e.g., canonical content items such as cloud-based orcloud-backed content items, third-party cloud service content itemsassociated with canonical content items, etc.) and/or associated data orrequest restoration of such content items and/or associated data fromthe cloud services (e.g., 302, 304, 306, 170); commenting operations;operations to generate and/or present previews of canonical contentitems (e.g., cloud-based or cloud-backed content items); operations toshare canonical content items (e.g., cloud-based or cloud-backed contentitems) and/or associated data; operations to revert to previous versionsof canonical content items (e.g., cloud-based or cloud-backed contentitems); operations to modify (rename, move, delete, edit, etc.)canonical content items (e.g., cloud-based or cloud-backed contentitems); and so forth.

Cloud integration service 320 can communicate with filesystem 148 tostore or access metadata associated with canonical content items (e.g.,cloud-based or cloud-backed content items) from the cloud services(e.g., 302, 304, 306, 170). Filesystem 148 can store and provide suchmetadata for use by cloud integration service 320 and any other servicein content management system 110. The metadata can include, for exampleand without limitation, information regarding changes to the canonicalcontent items (e.g., cloud-based or cloud-backed content items), accessinformation associated with the canonical content items, data logsassociated with the canonical content items, unique identifiers (IDs)associated with the canonical content items, description informationassociated with the canonical content items, version numbers orinformation associated with the canonical content items, timestampsassociated with filesystem entries corresponding to the canonicalcontent items, change history information for the canonical contentitems, pointers to content associated with the canonical content items,folders, file paths, etc.

Cloud integration service 320 can also communicate with metadata store146 to update or retrieve metadata and objects in metadata store 146.Metadata store 146 can store other metadata and objects such as entitiesor associations pertaining to user accounts, canonical content items(e.g., cloud-based or cloud-backed content items), user groups,namespaces, memberships, etc. For example, metadata store 146 may store,without limitation, metadata describing content items (e.g., traditionalcontent items, cloud-based content items, cloud-backed content items),content item types, comments, indexing data, access permissions, user orgroup memberships, sharing information, etc. In some examples, metadatastore 146 can also store information describing the relationship ofcontent items (e.g., traditional content items, cloud-based contentitems, cloud-backed content items) to one or more accounts, collections,groups, namespaces, folders, team entities, etc., in metadata store 146.

Cloud integration service 320 can communicate with content storage 142to store and/or retrieve content from content storage 142. Cloudintegration service 320 can store and retrieve content from thecloud-based or cloud-backed content items and/or representations ofcloud-based or cloud-backed content items, such as smart pointers andcanonical content items as further described below. For example, in somecases, content storage 142 may store the content of one or morecloud-based or cloud-backed content items for access to the contentdirectly from content storage 142. In this example, cloud integrationservice 320 may retrieve, store, or update such content in contentstorage 142.

In other examples, content storage 142 may only store representations ofone or more cloud-based or cloud-backed content items. For example,content storage 142 may only store a smart pointer referencing acloud-based or cloud-backed content item stored on a cloud service(e.g., 302, 304, 306, 170) as further described below. In this example,the representations (e.g., smart pointers) of the cloud-based orcloud-backed content items may be retrieved from content storage 142 andprovided to client devices requesting access to the cloud-based orcloud-backed content items, but some or all of the actual content in thecloud-based or cloud-backed content items may not be included in therepresentations and instead obtained from respective cloud services(e.g., 302, 304, 306, 170) as further described below.

Cloud integration service 320 can also communicate with events store 143to store, retrieve, and/or update activity and event informationassociated with content items such as canonical content items (e.g.,cloud-based or cloud-backed content items) or smart pointers. Cloudintegration service 320 can monitor events or activity from events store143, obtain status information associated with content items (e.g.,canonical content items such as cloud-based or cloud-backed contentitems, smart pointers, etc.) from events store 143, process eventsand/or metrics based on information in events store 143, generate orprovide notifications or alerts based on information in events store143, etc.

FIG. 5A shows example functionality mapping 500 between third-partycloud service content item 502 on third-party cloud service 302 andsmart pointer 504 in content management system 110. Third-party cloudservice content item 502 can be a cloud-based or cloud-backed contentitem hosted by third-party cloud service 302. In some cases, third-partycloud service content item 502 can be a cloud-based content item hostedby the third-party cloud service 302 and created for (or using) acloud-based application or editor, such as a web-based application oreditor. In other cases, third-party cloud service content item 502 canbe a cloud-backed content item hosted by the third-party cloud service302 and created for (or using) a client application, a nativeapplication associated with the cloud-backed content item, or acloud-based application or editor.

Third-party cloud service content item 502 can include specificformatting, content, features, and functionalities supported bythird-party cloud service 302 and the cloud-based application ordocument editor associated with third-party cloud service content item502. For example, third-party cloud service content item 502 can includea specific type of data or content, specific sharing features, specificonline collaboration features, specific web-publishing features,specific reviewing features, specific document or user behaviorfunctionalities, etc. In some examples, third-party cloud servicecontent item 502 can include specific formatting, content, features, andfunctionalities supported by a client or native software application, aswell as additional functionalities and/or features supported by thethird-party cloud service 302. For example, the third-party cloudservice content item 502 can be a cloud-backed content item thatincludes specific formatting, content, features, and functionalities(e.g., filesystem operations, etc.) supported by a client or nativesoftware application, as well as additional features or functionalitiesenabled by third-party cloud service 302, such as collaborationfunctionalities (e.g., live editing, commenting, messaging, activitynotifications, etc.).

In some cases, the content, features, and/or functionalities ofthird-party cloud service content item 502 are supported throughthird-party cloud service 302 and a specific cloud-based application oreditor associated with third-party cloud service content item 502, butits content and functionalities can also be obtained through smartpointer 504 as further described herein. For example, the content,features, and/or functionalities of third-party cloud service contentitem 502 may be specifically designed for, and supported by, third-partycloud service 302 and an associated cloud-based application or editor,but its content (and associated functionalities) may also beaccessed/rendered, edited, etc., through smart pointer 404 on contentmanagement system 110 (and/or client application 152).

In some examples, the content, features, and/or functionalities ofthird-party cloud service content item 502 may be partially or fullyaccessible and supported by other applications (e.g., applications otherthan a cloud-based application or editor provided by third-party cloudservice 302 for third-party cloud service content item 502), such aslocal and/or file-based applications or content editors. For example,third-party cloud service content item 502 can be a cloud-backed contentitem and at least some of its content, features, and/or functionalitiescan be accessed through a client application while additionalfunctionalities can be accessed through third-party cloud service 302.In some cases, users may access/render the content in third-party cloudservice content item 502 from smart pointer 504, and may access some orall of the features or functionalities of third-party cloud servicecontent item 502 from third-party cloud service 302.

Smart pointer 404 can be a representation of third-party cloud servicecontent item 502 stored in content management system 110 for access byclient devices (e.g., 150) having accounts on content management system110. For example, smart pointer 504 may appear as another content itemstored in content management system 110 but may not include the actualcontent of third-party cloud service content item 502. Instead, smartpointer 504 may reference third-party cloud service content item 502 andprovide access to the actual content of third-party cloud servicecontent item 502 from smart pointer 504 on content management system110. In some cases, in addition to providing access to the content ofthird-party cloud service content item 502, smart pointer 504 can alsoprovide access to cloud-based functionalities provided by third-partycloud service 302 and/or enable other functionalities supported bycontent management system 110, such as previews, searching, commenting,etc.

In some cases, smart pointer 504 can provide organization and/or accessprimitives associated with content management system 110, while allowingthird-party cloud service 302 to continue to provide its ownorganization and/or access models in addition to those associated withcontent management system 110. For example, a user may be able to renamesmart pointer 504, copy smart pointer 504 to another location in contentmanagement system 110, move smart pointer 504 to another location incontent management system 110, add smart pointer 504 to a shared folderin content management system 110, etc. Moreover, content managementsystem 110 can provide additional features and/or functionalities tosmart pointer 504, as further described below.

In some examples, when smart pointer 504 is invoked by a client device(e.g., 150), the client device can launch an instance of third-partycloud service content item 502. The instance of the third-party cloudservice content item 502 can obtain and present, using cloud integrationservice 320, the content of third-party cloud service content item 502.Here, cloud integration service 320 can obtain such content fromthird-party cloud service 302. In some examples, cloud integrationservice 320 can also obtain one or more functionalities from third-partycloud service 302, for provisioning via the instance of the third-partycloud service content item 522. The launched instance may present orrender the content of third-party cloud service content item 502 andprovide access to the features or functionalities of third-party cloudservice content item 502, without storing the actual content ofthird-party cloud service content item 502.

Thus, from the user's perspective, when smart pointer 504 is launchedfrom the user's client device, the user experience in this example maybe similar or identical to the experience when third-party cloud servicecontent item 502 is actually accessed from third-party cloud service 302through an associated cloud-based application or editor. Therefore,while smart pointer 504 may not store the actual content fromthird-party cloud service content item 502, the user experience whenaccessing smart pointer 504 may be indistinguishable (or almostindistinguishable) from the user experience when third-party cloudservice content item 502 is accessed directly from third-party cloudservice 302 through an associated cloud-based application or editor.

In some cases, smart pointer 502 may include certain content and/ormetadata associated with third-party cloud service content item 502,such as indexable content 506A, previews 506B, comments 506N, etc. Forexample, content management system 110 may obtain (e.g., fromthird-party cloud service 302 and/or via cloud integration service 320)content and/or metadata associated with third-party cloud servicecontent item 502, which content management system 110 can use togenerate and/or store indexable content 506A, previews 506B, comments506N, and/or any other relevant information.

Indexable content 506A can include one or more portions of content ormetadata associated with third-party cloud service content item 502,which can be used by content management system 110 (and/or client device150) for indexing and searching of data associated with third-partycloud service content item 502. Previews 506B can be used to generate arendered preview of third-party cloud service content item 502 withoutlaunching an entire instance of third-party cloud service content item502. Comments 506N can be used to associate third-party cloud servicecontent item 502 and/or content in third-party cloud service contentitem 502 with specific comments provided by one or more users withaccess to third-party cloud service content item 502. Comments 506N canallow various user comments created through third-party cloud service302 and/or content management system 110 to be presented and/oridentified when a user accesses smart pointer 504.

Content management system 110 may manage or control various features orfunctionalities on content management system 110 for smart pointer 504,such as the storage and organization of smart pointer 504 within a useraccount and/or client device, access control permissions (e.g., readpermissions, edit permissions, sharing permissions, etc.) for smartpointer 504, etc. In some cases, content management system 110 mayextend the features and/or functionalities provided by third-party cloudservice 302 for third-party cloud service content item 502, and thusassociated with smart pointer 504, to include one or more features orfunctionalities supported by content management system 110, such assharing functionalities, synchronization functionalities, local storagefunctionalities, events or notification functionalities, commentingfunctionalities, rating functionalities, collaboration functionalities,etc.

Moreover, content management system 110 may control or manage where andhow smart pointer 504 is depicted within a user account or contentorganizational structure (e.g., hierarchical organization, folder orfilesystem based organization, etc.). For example, content managementsystem 110 can depict smart pointer 502 within a particular folder,collection, or location on the user account and/or client device as in away that appears as if third-party cloud service content item 502 andits associated content is being stored through content management system110 according to a specific organization or storage scheme associatedwith a user's content in content management system 110.

FIG. 5B shows example functionality mapping 524 between canonicalcontent item 520 in content management system 110 and third-party cloudservice content item 522 and/or functionalities associated withcanonical content item 520 provided or supported by third-party cloudservice 302. Canonical content item 520 can represent a cloud-based orcloud-backed content item stored in content management system 110 and/orthird-party cloud service 302. Moreover, canonical content item 520 canprovide access by client devices (e.g., 150) having accounts on contentmanagement system 110 to content and functionalities associated withcanonical content item 520 (e.g., content and functionalities of acloud-based or cloud-backed content item associated with canonicalcontent item 520).

In some cases, canonical content item 520 can include some or all of theactual content associated with canonical content item 520. In otherwords, canonical content item 520 can be stored in content managementsystem 110 along with its actual content. Moreover, canonical contentitem 520 can be stored in one or more user accounts on contentmanagement system 110 and can appear to a user as another content itemin the user account. In some cases, third-party cloud service 302 canalso store a copy or version of the cloud-backed or cloud-based contentitem represented by canonical content item 520, as depicted bythird-party cloud service content item 522 in FIG. 5B.

In some cases, canonical content item 520 can be a cloud-backed contentitem stored on content management system 110 and capable of obtainingadditional functionalities, such as real-time collaboration, fromcontent management system 110 and/or third-party cloud service 302.Canonical content item 520 can obtain functionalities from third-partycloud service 302 via cloud integration service 320. To illustrate, inone example, canonical content item 520 can represent a cloud-backedcontent item stored on, and accessible from, content management system110 that supports a set of functionalities, such as view and editfunctionalities, irrespective of any cloud service (e.g., 302) orcloud-based functionalities (e.g., 402). However, in this example, whencanonical content item 520 is accessed from content management system110 (or a client device associated with content management system 110),cloud integration service 320 can communicate with third-party cloudservice 302 to obtain one or more cloud-based functionalities forcanonical content item 520 from third-party cloud service 302. Thus,despite canonical content item 520 not being stored on third-party cloudservice 302, content management system 110 can nevertheless integrateinto canonical content item 520 additional functionalities provided orsupported by third-party cloud service 302.

In some cases, canonical content item 520 can be a cloud-based contentitem stored on content management system 110 and capable of renderingthe content of the cloud-based content items and providing itsassociated functionalities, such as real-time collaboration. In thisexample, cloud integration service 320 can communicate with third-partycloud service 302 to obtain the content and functionalities associatedwith the cloud-based content item represented by canonical content item520. This can allow canonical content item 520 to render the cloud-basedcontent item and provide its associated functionalities even if thecloud-based content item is not native to content management system 110and/or would otherwise require a specific application or editor fromthird-party cloud service 302 for rendering and interacting with thecloud-based content item.

To illustrate, in one example, canonical content item 520 can representa cloud-based content item stored on, and accessible from, contentmanagement system 110 that traditionally could only be rendered andsupported by a specific cloud-based application or editor fromthird-party cloud service 302. However, in accordance with some aspectsof the present technology, when canonical content item 520 is accessedfrom content management system 110 (or a client device associated withcontent management system 110), cloud integration service 320 cancommunicate with third-party cloud service 302 to obtain data andcloud-based functionalities for canonical content item 520 fromthird-party cloud service 302. Cloud integration service 320 can thenrender the cloud-based content item through canonical content item 520and provide associated cloud-based functionalities supported bythird-party cloud service 302. Thus, despite canonical content item 520not being stored on third-party cloud service 302 or accessed from acloud-based application or editor associated with third-party cloudservice 302, content management system 110 can nevertheless render thecloud-based content item represented by canonical content item 520 andintegrate associated functionalities provided or supported bythird-party cloud service 302.

In some cases, canonical content item 520 may include certain contentand/or metadata associated with the cloud-based or cloud-backed contentitem it represents, such as indexable content 526A, previews 526B,comments 526N, etc. For example, content management system 110 mayobtain (e.g., from third-party cloud service 302 or content storage 142,and/or via cloud integration service 320) content and/or metadataassociated with canonical content item 520, which content managementsystem 110 can use to generate and/or store indexable content 526A,previews 526B, comments 526N, and/or any other relevant information.

Indexable content 526A can include one or more portions of content ormetadata associated with canonical content item 520 and/or thecloud-based or cloud-backed content item represented by canonicalcontent item 520, which can be used for indexing and searching of dataassociated with canonical content item 520. Previews 526B can be used togenerate a rendered preview of canonical content item 520 and/or thecloud-based or cloud-backed content item represented by canonicalcontent item 520, without launching an entire instance of canonicalcontent item 520. Comments 526N can be used to associate canonicalcontent item 520 and/or the content of the cloud-based or cloud-backedcontent item represented by canonical content item 520, with specificcomments provided by one or more users with access to canonical contentitem 520 and/or the cloud-based or cloud-backed content item representedby canonical content item 520. Comments 406N can allow various usercomments created through third-party cloud service 302 and/or contentmanagement system 110 to be presented and/or identified when a useraccesses canonical content item 520.

Content management system 110 may manage or control various features orfunctionalities on content management system 110 for canonical contentitem 520, such as the storage and organization of canonical content item520 within a user account and/or client device, access controlpermissions (e.g., read permissions, edit permissions, sharingpermissions, etc.) for canonical content item 520, etc. In some cases,content management system 110 may extend the features and/orfunctionalities provided by third-party cloud service 302 for thecloud-based or cloud-backed content item represented by canonicalcontent item 520 to include one or more features or functionalitiessupported by content management system 110, such as sharingfunctionalities, synchronization functionalities, local storagefunctionalities, events or notification functionalities, commentingfunctionalities, rating functionalities, collaboration functionalities,etc. Thus, in some cases, canonical content item 520 can obtainfunctionalities and features from both third-party cloud service 302 andcontent management system 110.

Moreover, content management system 110 may control or manage where andhow canonical content item 520 is depicted within a user account orcontent organizational structure (e.g., hierarchical organization,folder or filesystem based organization, etc.). For example, contentmanagement system 110 can depict canonical content item 502 within aparticular folder, collection, or location on the user account and/orclient device (e.g., 150), and/or according to a specific organizationor storage scheme associated with a user's content in content managementsystem 110.

FIG. 5C shows an example basic pointer (530) on content managementsystem 110. In this example, basic pointer 530 references third-partycloud service content item 534 on third-party cloud service 302. Basicpointer 530 may not include the actual content of third-party cloudservice content item 534, but rather includes an address 532 foraccessing third-party cloud service content item 534 on third-partycloud service 302 from basic pointer 530. In some examples, address 532can be a URL associated with third-party cloud service content item 534,and basic pointer 530 can be a light wrapper around the URL. When a userselects or activates basic pointer 530, the user can be directed byaddress 534 to third-party cloud service content item 534 on third-partycloud service 302. The user can then access third-party cloud servicecontent item 534 from third-party cloud service 302.

Thus, in some cases, basic pointer 530 can function similar to a link orbookmark for accessing third-party cloud service content item 534 onthird-party cloud service 302. However, content management system 110can manage the organization and/or access to basic pointer 530 fromcontent management system 110, and can depict or provide basic pointer530 within a user account on content management system 110 as anothercontent item.

FIG. 6A shows example user experiences and use cases of smart pointer504 being accessed through browser application 166 on client device 150₁ and third-party cloud service content item 502 being accessed throughbrowser application 166 on client device 150 ₂. In this example, a useron client device 150 ₁ can access the content of third-party cloudservice content item 502 through smart pointer 504 and a user on clientdevice 150 ₂ can access the content of third-party cloud service contentitem 502 directly from third-party cloud service 302.

Smart pointer 504 can be accessed from client device 150 ₁ throughbrowser application 166. Prior to being launched or invoked, smartpointer 504 can appear to the user as a copy of third-party cloudservice content item 502. When client device 150 ₁ invokes or launchessmart pointer 504 through browser application 166, browser application166 can receive the content of third-party cloud service content item502 from third-party cloud service 302 and present the content asrendered content 602. Rendered content 602 can display the content ofthird-party cloud service content item 502, enable access to featuresand functionalities of third-party cloud service content item 502, andprovide a user experience that is similar or identical to the userexperience when third-party cloud service content item 502 is accesseddirectly from third-party cloud service 302 through a correspondingcloud-based application or document editor. Rendered content 602 mayresemble or mirror the layout of third-party cloud service content item502, the formatting of third-party cloud service content item 502, thefeatures of third-party cloud service content item 502, etc., and maydepict the content of third-party cloud service content item 502 asconfigured in third-party cloud service content item 502.

On the other hand, client device 150 ₂ is depicted accessing third-partycloud service content item 502 directly from third-party cloud service302 through browser application 166. In this example, to accessthird-party cloud service content item 502 from client device 150 ₂,browser application 166 implements third-party cloud service application604, which can be, for example, a web or cloud-based application oreditor provided by third-party cloud service 302 for third-party cloudservice content item 502 and other cloud-based or cloud-backed contentitems that are the same or similar type as third-party cloud servicecontent item 502.

Third-party cloud service application 604 can communicate withthird-party cloud service 302 to retrieve the content and features ofthird-party cloud service content item 502 and provide an onlinerendering of third-party cloud service content item 502. Thus, throughthird-party cloud service application 604, browser application 166 onclient device 150 ₂ can present rendered third-party cloud servicecontent item 608 depicting third-party cloud service content item 502,including its content and features. The user experience in this exampleis similar or identical to the user experience associated with smartpointer 504 at client device 150 _(k), but the access and process isdifferent, with client device 150 ₂ implementing third-party cloudservice application 604 to access the content and features ofthird-party cloud service content item 502 from third-party cloudservice 302.

Moreover, smart pointer 504 allows a representation of third-party cloudservice content item 502 to be stored on content management system 110along with other user content items, and allows third-party cloudservice content item 502 to be accessed by users from content managementsystem 110 through smart pointer 504. Thus, using smart pointers such assmart pointer 504, users can maintain, organize and access their contentitems on content management system 110 and their content items fromdifferent cloud services and providers (e.g., 302, 304, 306, 170) fromcontent management system 110. This way, users can have their contentitems stored and accessible from a single system (e.g., 110), and canavoid having to go to disparate cloud services to access differentcontent items.

Further, in some cases, smart pointer 504 can enable content managementsystem (CMS) interface features 606 for rendered content 602 on clientdevice 150 ₁ CMS interface features 606 can include features orfunctionalities provided through content management system 110 on top ofthose features or functionalities provided by third-party cloud service302 for third-party cloud service content item 502. For example,rendered content 602 can be extended to include one or more features(e.g., 606) supported or provided by content management system 110, suchas a feature for ranking or rating rendered content 602 or portions ofrendered content 602, a notifications feed for accessing activitynotifications and/or alerts associated with rendered content 602 and/orthird-party cloud service content item 502, collaboration features suchas co-authoring and chatting, commenting features, sharing features,etc. Thus, smart pointer 504 can not only enable users to access fromcontent management system 110 the content and functionalities providedby third-party cloud service 302 for third-party cloud service contentitem 502, but also additional features and functionalities provided orsupported by content management system 110.

FIG. 6B shows example user experiences and use cases of canonicalcontent item 520 being accessed through browser application 166 onclient device 150 ₁ and third-party cloud service content item 502 beingaccessed through browser application 166 on client device 150 ₂. In thisexample, a user on client device 150 ₁ can access the content ofthird-party cloud service content item 502 through canonical contentitem 520 and a user on client device 150 ₂ can access the content ofthird-party cloud service content item 402 directly from third-partycloud service 302.

Canonical content item 520 can be accessed from client device 150 ₁through browser application 166. Canonical content item 520 canrepresent third-party cloud service content item 502 and can include thecontent of third-party cloud service content item 502. Third-party cloudservice content item 502 can be a cloud-based or cloud-backed contentitem. Moreover, because canonical content item 520 can include thecontent of third-party cloud service content item 502, when clientdevice 150 ₁ invokes or launches canonical content item 520 throughbrowser application 166, browser application 166 can obtain the contentof third-party cloud service content item 402 from content managementsystem 110 and/or canonical content item 520, and present the content asrendered content 610. Thus, browser application 166 can present renderedcontent 610 without directly accessing such content from third-partycloud service 302.

Rendered content 610 can display the content as part of canonicalcontent item 520, enable access to features and functionalities ofthird-party cloud service content item 502 provided or supported bythird-party cloud service 302, and provide a user experience that issimilar or identical to the user experience when third-party cloudservice content item 502 is accessed directly from third-party cloudservice 302 through a corresponding cloud-based application or editor.Rendered content 610 may resemble or mirror the layout of third-partycloud service content item 502, the formatting of third-party cloudservice content item 502, the features of third-party cloud servicecontent item 502, etc., and may depict the content (e.g., renderedcontent 610) of third-party cloud service content item 502 as configuredin third-party cloud service content item 502.

On the other hand, client device 150 ₂ is depicted accessing third-partycloud service content item 502 directly from third-party cloud service302 through browser application 166. To access third-party cloud servicecontent item 502 from client device 150 ₂, browser application 166implements third-party cloud service application 604, which can be, forexample, a web or cloud-based application or editor provided bythird-party cloud service 302 for third-party cloud service content item502 and other cloud-based or cloud-backed content items that are thesame or similar type as third-party cloud service content item 502.

Third-party cloud service application 604 can communicate withthird-party cloud service 302 to retrieve the content and features ofthird-party cloud service content item 502 and provide an onlinerendering of third-party cloud service content item 502. Thus, throughthird-party cloud service application 604, browser application 166 onclient device 150 ₂ can present rendered third-party cloud servicecontent item 608 depicting third-party cloud service content item 502,including its content and features. The user experience in this exampleis similar or identical to the user experience associated with canonicalcontent item 520 at client device 150 ₁, but the access and process isdifferent, with client device 150 ₂ implementing third-party cloudservice application 604 to access the content and features ofthird-party cloud service content item 502 from third-party cloudservice 302.

Moreover, canonical content item 520 allows a representation andassociated content of third-party cloud service content item 502 to bestored on content management system 110 along with other user contentitems, and allows the content and features of third-party cloud servicecontent item 502 to be accessed by users from content management system110 through canonical content item 520. Thus, using canonical contentitems such as canonical content item 520, users can maintain, organizeand access their content items on content management system 110 andtheir content items from different cloud services and providers (e.g.,302, 304, 306, 170) from content management system 110. This way, userscan have their content items stored and accessible from a single system(e.g., 110), and can avoid having to go to disparate cloud services toaccess different content items.

Further, in some cases, canonical content item 520 can enable CMSinterface features 606 for rendered content 610 on client device 150 ₁.CMS interface features 606 can include features or functionalitiesprovided through content management system 110 on top of those featuresor functionalities provided by third-party cloud service 302 forthird-party cloud service content item 502. For example, renderedcontent 610 provided through canonical content item 520 can be extendedto include one or more features (e.g., 606) supported or provided bycontent management system 110, such as content ranking or ratingfeatures, a notifications feed for accessing activity notificationsand/or alerts associated with rendered content 610 and/or third-partycloud service content item 502, collaboration features such asco-authoring and chatting, commenting features, sharing features, etc.Thus, canonical content item 520 can not only enable users to accessfrom content management system 110 the content and functionalitiesprovided by third-party cloud service 302 for third-party cloud servicecontent item 502, but also additional features and functionalitiesprovided or supported by content management system 110.

FIG. 6C shows other example user experiences and use cases of smartpointer 504 being accessed through client application 152 on clientdevice 150 ₁ and third-party cloud service content item 502 beingaccessed through browser application 166 on client device 150 ₂. Theuser experience and use case of third-party cloud service content item502 being accessed through browser application 166 and third-party cloudservice application 604 on client device 150 ₂ is the same as shown inFIGS. 6A and 6B, but is provided in this example to depict thedifferences and similarities in the process and user experience in thisuse case relative to the example use case when smart pointer 504 isaccessed through client application 152 on client device 150 ₁.

As shown in FIG. 6C, a user on client device 150 ₁ can access thecontent of third-party cloud service content item 502 through smartpointer 504 and client application 152, as opposed to accessing thecontent of third-party cloud service content item 502 directly fromthird-party cloud service 302 using browser application 166 andthird-party cloud service application 604 as depicted with respect toclient device 150 ₂. Prior to being launched or invoked, smart pointer504 can appear to the user as a copy of third-party cloud servicecontent item 502 available on content management system 110 throughclient application 152. When client device 150 ₁ invokes or launchessmart pointer 504 through client application 152, client application 152can receive the content of third-party cloud service content item 502from third-party cloud service 302 and present the content on interface620 as rendered content 602.

Interface 620 can be an interface provided by client application 152,the operating system or windowing system at client device 150 ₁, and/orany other tool or software at client device 150 ₁. Rendered content 602can display the content of third-party cloud service content item 502,enable access to features and functionalities of third-party cloudservice content item 502, and provide a user experience that is similaror identical to the user experience when third-party cloud servicecontent item 502 is accessed directly from third-party cloud service 302through a corresponding cloud-based application or editor. Renderedcontent 602 may resemble or mirror the layout of third-party cloudservice content item 502, the formatting of third-party cloud servicecontent item 502, the features of third-party cloud service content item502, etc., and may depict the content (e.g., 602) of third-party cloudservice content item 502 as configured in third-party cloud servicecontent item 502.

Moreover, client application 152 may depict smart pointer 504 as acontent item locally stored in the filesystem of client device 150 ₁. Insome cases, smart pointer 504 may not include all or any of the actualcontent of third-party cloud service content item 502, as previouslyexplained. However, client application 152 may depict smart pointer 504on client device 150 ₁ as if all the actual content of third-party cloudservice content item 502 is also stored as part of smart pointer 504.Thus, the user at client device 150 ₁ may be unaware that smart pointer504 does not actually store all the content of third-party cloud servicecontent item 502.

Further, as previously mentioned, smart pointer 504 allows arepresentation of third-party cloud service content item 502 to bestored on content management system 110 and client device 150 ₁ alongwith other user content items, and allows third-party cloud servicecontent item 502 to be accessed by users from content management system110 or client device 150 ₁ through smart pointer 504. Thus, using smartpointers such as smart pointer 504, users can maintain, organize andaccess their content items stored on client device 150 ₁ and contentmanagement system 110, as well as their content items on different cloudservices and providers (e.g., 302, 304, 306, 170), from client device150 ₁ and content management system 110. This way, users can have theircontent items stored and accessible from a single system (e.g., 110,150), and can avoid having to go to disparate cloud services to accessdifferent content items.

In some cases, smart pointer 504 can enable CMS interface features 606for rendered content 602 on client device 150 ₁. As previouslyexplained, CMS interface features 606 can include features orfunctionalities provided through content management system 110 on top ofthose features or functionalities provided by third-party cloud service302 for third-party cloud service content item 502. Thus, smart pointer504 can not only enable users to access from client application 152 onclient device 150 ₁ the content and functionalities provided bythird-party cloud service 302 for third-party cloud service content item502, but also additional features and functionalities provided orsupported by content management system 110.

FIG. 6D shows other example user experiences and use cases of canonicalcontent item 520 being accessed through client application 152 on clientdevice 150 ₁ and third-party cloud service content item 502 beingaccessed through browser application 166 on client device 150 ₂. Theuser experience and use case of third-party cloud service content item502 being accessed through browser application 166 and third-party cloudservice application 604 on client device 150 ₂ is the same as shown inFIGS. 6A and 6B, but is provided in this example to depict thedifferences and similarities in the process and user experience in thisuse case relative to the example use case when canonical content item520 is accessed through client application 152 on client device 150 ₁.

As shown in FIG. 6D, a user on client device 150 ₁ can access thecontent of third-party cloud service content item 502 through canonicalcontent item 520 and client application 152, as opposed to accessing thecontent of third-party cloud service content item 502 directly fromthird-party cloud service 302 using browser application 166 andthird-party cloud service application 604 as depicted with respect toclient device 150 ₂. In some cases, canonical content item 520 can storeor include the actual content of third-party cloud service content item502. Moreover, in some cases, canonical content item 520 can represent acloud-based or cloud-backed content item. Here, canonical content item520 may store the actual contents of the cloud-based or cloud-backedcontent item, but may obtain additional features or functionalities fromthird-party cloud service 302, as described herein.

Canonical content item 520 can appear to the user as a copy ofthird-party cloud service content item 502 available on contentmanagement system 110 through client application 152. When client device150 ₁ invokes or launches canonical content item 520 through clientapplication 152, client application 152 can obtain or access its contentand present it on interface 620 as rendered content 610. Canonicalcontent item 520 can also present (e.g., via interface 620) or provideadditional features or functionalities obtained from third-party cloudservice 302 (e.g., via cloud integration service 320).

Rendered content 610 can display the content of canonical content item520 (e.g., stored on content management system 110 or obtained fromthird-party cloud service 302), enable access to features andfunctionalities of third-party cloud service 302 and/or third-partycloud service content item 502, and provide a user experience that issimilar or identical to the user experience when third-party cloudservice content item 502 is accessed directly from third-party cloudservice 302 through a corresponding cloud-based application or editor.Rendered content 610 may resemble or mirror the layout of third-partycloud service content item 502, the formatting of third-party cloudservice content item 502, the features of third-party cloud servicecontent item 502, etc., and may depict the content (e.g., 602) ofthird-party cloud service content item 502 as configured in third-partycloud service content item 502.

Moreover, client application 152 may depict canonical content item 520as a content item locally stored in the filesystem of client device 150₁. In some cases, the filesystem can not only store a representation orinstance of canonical content item 520 but also the content associatedwith canonical content item 520. Further, as previously mentioned,canonical content item 520 can be stored on content management system110 and client device 150 ₁ along with other user content items, andallows canonical content item 520 and its associated contents to beaccessed by users from client device 150 ₁ through canonical contentitem 520. Thus, using canonical content items such as canonical contentitem 520, users can maintain, organize and access their content itemsstored on client device 150 ₁ and content management system 110, as wellas their content items on different cloud services and providers (e.g.,302, 304, 306, 170), from client device 150 ₁ and content managementsystem 110. This way, users can have their content items stored andaccessible from a single system (e.g., 110, 150), and can avoid havingto go to disparate cloud services to access different content items.

Further, in some cases, canonical content item 520 can support CMSinterface features 606 for rendered content 610 on client device 150 ₁.As previously explained, CMS interface features 606 can include featuresor functionalities provided through content management system 110 on topof those features or functionalities provided by third-party cloudservice 302 for canonical content item 520. Thus, canonical content item520 can not only enable users to access from client application 152 onclient device 150 ₁ the content and functionalities provided bythird-party cloud service 302 for canonical content item 520, but alsoadditional features and functionalities provided or supported by contentmanagement system 110.

As shown in FIGS. 6A through 6D, browser application 166 and clientapplication 152 can present third-party cloud service content item 502(e.g., rendered content 602, 610) on client device 150 ₁ without the useor need of third-party cloud service application 604. Thus, thetechniques herein allow content management system 110 to provide clientdevice 150 ₁ access to the content and features of third-party cloudservice 302 and/or third-party cloud service content item 502 withoutimplementing or using an application that natively supports third-partycloud service content item 502, such as third-party cloud serviceapplication 604.

FIG. 7A shows an example process 700 for providing a representation(e.g., smart pointer 504) of third-party cloud service content item 502in content management system 110, and providing client device 150 accessto the content and functionalities of third-party cloud service contentitem 502 through smart pointer 504 on content management system 110.

In this example, smart pointer 504 is stored in user account 704 oncontent management system 110. User account 704 can be a user accountregistered on content management system 110, which contains contentitems stored and maintained by the user on content management system110. In some cases, the content items, including smart pointer 504, inuser account 704 can also be stored and synchronized locally on clientdevice 150 as previously explained. Thus, while smart pointer 504 isdepicted in FIG. 7A as being stored in content management system 110, inother examples smart pointer 504 may also be stored and accessed locallyon client device 150, as shown in FIG. 7B and further described below.

In process 700, browser application 166 on client device 150 first sendsrequest 706 to content management system 110 for the content and/ormetadata associated with smart pointer 504. Content management system110 can receive request 706 and send response 708 to browser application166, which browser application 166 can use to continue with process 700to render/present a representation of third-party cloud service contentitem 502 on client device 150. Response 708 can include, for example,metadata associated with third-party cloud service content item 502,which browser application 166 can use to present or render arepresentation of third-party cloud service content item 502.

For example, response 708 can include an identifier (ID) that can beused to request the content of third-party cloud service content item502 from third-party cloud service 302, authentication information(e.g., an authentication token) that can be used to authenticatethird-party cloud service 302 with content management system 110 toallow the flow of data (e.g., third-party cloud service content item502, associated metadata, associated content, etc.) and/orcommunications between content management system 110 and third-partycloud service 302, a title identifying third-party cloud service contentitem 502, access control permissions configured for user account 704that define the level of access to the content of third-party cloudservice content item 502 configured for user account 704, an address orresource identifier for requesting or obtaining the content ofthird-party cloud service content item 502 from third-party cloudservice 302, and/or any other information or metadata associated withcanonical content item 520.

Browser application 166 can receive response 708 from content managementsystem 110 and send, via cloud content integration element 702, request710 to third-party cloud service 302 for content and/or data associatedwith third-party cloud service content item 502. Cloud contentintegration element 702 can be an interface and/or communication elementwithin browser application 166 configured to communicate withthird-party cloud service 302 to receive content and data associatedwith third-party cloud service content item 502 and exchange withthird-party cloud service 302 updates, metadata, and/or any otherinformation associated with third-party cloud service content item 502.In some cases, cloud content integration element 702 can be a page, anIFrame (inline frame), an interface or web page element, a plugin, abrowser tool or element, or software code that is implemented orexecuted by browser application 166 to communicate with third-partycloud service 302 and provide access to content and functionalities ofthird-party cloud service content item 502 through browser application166 on client device 150. Cloud content integration element 702 can beconfigured to send and/or receive calls or requests for content andinformation associated with third-party cloud service content item 502to and/or from third-party cloud service 302.

As previously noted, cloud content integration element 702 can sendrequest 710 to third-party cloud service 302 for content and informationassociated with third-party cloud service content item 502. Request 710can include, for example, an ID uniquely identifying third-party cloudservice content item 502 at third-party cloud service 302,authentication information (e.g., a token for third-party cloud service302 to use to authenticate with content management system 110), a titleidentifying third-party cloud service content item 502, access controlinformation indicating a level of access to content associated withthird-party cloud service content item 502 defined for user account 704and/or client device 150, metadata associated with third-party cloudservice content item 502 and/or user account 704, and/or any otherinformation associated with third-party cloud service content item 502and/or user account 704.

Cloud content integration element 702 can receive response 712 fromthird-party cloud service 302. Response 712 can include data associatedwith third-party cloud service content item 502, such as the content inthird-party cloud service content item 502, metadata (e.g., comments,preview(s), indexable content, state information, descriptioninformation, access information, status or activity information, userinformation, etc.) associated with third-party cloud service contentitem 502, etc.

Cloud content integration element 702 and browser application 166 canuse the data in response 712 to render 714 third-party cloud servicecontent item 502 or a representation of third-party cloud servicecontent item 502 in browser application 166. At this point, a user atclient device 150 can view, access and interact with the content andfeatures of third-party cloud service content item 502 from browserapplication 166. The user can read the content of third-party cloudservice content item 502, modify the content, add content, add or modifymetadata (e.g., comments, etc.), and otherwise interact with the contentand rendered representation of third-party cloud service content item502 from browser application 166 in a similar fashion as when the useraccesses third-party cloud service content item 502 directly fromthird-party cloud service 302 through a cloud-based application oreditor (e.g., 604) provided for third-party cloud service content item502. Process 700 can thus allow a user to access from content managementsystem 110 content and functionalities provided by third-party cloudservice 302 for cloud-based or cloud-backed content items (e.g.,third-party cloud service content item 502).

In some cases, cloud content integration element 702 can also send orreceive updates 716 to or from third-party cloud service 302 associatedwith third-party cloud service content item 502. Updates 716 can includechanges and/or information associated with third-party cloud servicecontent item 502, such as content or content changes (e.g., renameoperations, edit or write operations, delete operations, purgeoperations, move operations, restore operations, revert operations, addor create operations, etc.), metadata or events (e.g., comments, titleinformation or changes, IDs or ID changes, access information orpermissions, organization or storing information, membershipinformation, sharing information, user information, user activityinformation, tasks, timestamps, completed tasks or items, etc.), a tokento authenticate third-party cloud service 302 with content managementsystem 110, and so forth. In some examples, cloud content integrationelement 702 can receive updates 716 from third-party cloud service 302and implement such updates in the rendered third-party cloud servicecontent item on browser application 166, smart pointer 504, and/or useraccount 704.

In some cases, content management system 110 can similarly send orreceive updates 716 to or from third-party cloud service 302. Contentmanagement system 110 can, for example, send updates 716 when it detectschanges to content or metadata associated with third-party cloud servicecontent item 502 and can receive updates 716 when content or metadataassociated with third-party cloud service content item 502 are modifiedat third-party cloud service 302. Content management system 110 canimplement any changes to content or metadata received in updates 716from third-party cloud service 302. For example, content managementsystem 110 can update metadata associated with canonical content item520, such as comments, state, access information, storage information,or other information, based on updates 616 received from third-partycloud service 302. Updates 716 can thus synchronize or harmonizeinformation associated with third-party cloud service content item 502on third-party cloud service 302 and smart pointer 504 on contentmanagement system 110.

FIG. 7B shows an example process 720 for providing client device 150access to the content and functionalities of third-party cloud servicecontent item 502 through smart pointer 504 and client application 152 onclient device 150. In this example, smart pointer 504 is stored onclient device 150 along with other content items in user account 704registered on content management system 110. Process 720 allows a userto store and access the content and features of third-party cloudservice content item 502 from client application 152 (via smart pointer504) without use of an application, such as a cloud-based application oreditor, designed to natively support third-party cloud service contentitem 502.

In this example, client application 152 invokes 722 smart pointer 504 onclient device 150, and sends request 724 to content management system110 for authentication information associated with third-party cloudservice content item 502. Request 724 can include a unique identifierassociated with smart pointer 504 and third-party cloud service contentitem 502, as well as other information such as a title, user accountinformation, login information, metadata, etc. Content management system110 can receive request 724, verify permissions and/or authentication,and send response 726 to client application 152. Response 726 caninclude authentication information, such as an authentication tokenwhich third-party cloud service 302 can obtain and use to authenticatewith content management system 110 to send, receive, and/or requestcontent and metadata associated with third-party cloud service contentitem 502.

It should be noted that in some examples, client application 152 mayskip the process of sending request 724 to content management system 110and receiving response 726, and instead perform the remaining steps inprocess 720 without first sending request 724 and receiving response726. For example, client application 152 may already have anauthentication token or cached authentication information available andthus may not have to send request 724 to content management system 110.In some cases, client application 152 may send request 724 to contentmanagement system 110 if it determines it does not already have anauthentication token or other authentication information, or if anexisting authentication token or authentication information has expired,is invalid, or otherwise should be refreshed, updated, or replaced.

Client application 152 can implement or execute cloud contentintegration element 702 to communicate with third-party cloud service302 as previously described. Here, cloud content integration element 702can use the information in response 726, such as an authenticationtoken, a unique identifier, access control information, a title, etc.,to send request 728 to third-party cloud service 302 for the contentand/or metadata of third-party cloud service content item 502. Request728 can include, for example, authentication information and an ID thatthird-party cloud service 302 can use to authenticate, identify andretrieve content and/or metadata associated with third-party cloudservice content item 502, and send the content and/or metadata to cloudcontent integration element 702.

Cloud content integration element 702 can receive response 730 sent bythird-party cloud service 302. Response 730 can include the content inthird-party cloud service content item 502, metadata associated withthird-party cloud service content item 502, a token or authenticationinformation to authenticate with content management system 110, etc.Client application 152 and/or cloud content integration element 702 canuse the content and any metadata in response 730 to render 732 a copy orrepresentation of third-party cloud service content item 502 (e.g.,present the content of third-party cloud service content item 502 andany associated features or functionalities) on interface 620 at clientdevice 150, and provide support for any features or functionalitiesassociated with third-party cloud service content item 502. Interface620 can be any graphical user interface. For example, interface 620 canbe a user interface or a portion/section of a user interface provided byclient application 152, a user interface or window provided by anapplication on client device 150, a user interface or window provided byan operating system or windowing system on client device 150, a pagesuch as an HTML or other web page, etc.

At this point, the user at client device 150 can access and interactwith the content and features of third-party cloud service content item502 from interface 620 on client device 150. In some cases, process 720can include steps for exchanging updates and other information betweencloud content integration element 702, content management system 110,and/or third-party cloud service 302.

For example, if third-party cloud service 302 has updates associatedwith third-party cloud service content item 502, such as comments,content changes, metadata changes, etc., third-party cloud service 302can send message 734 including or requesting authentication informationfor authenticating with content management system 110 to provide suchupdates from third-party cloud service 302. In some cases, message 734can include authentication information (e.g., a token), identificationinformation (e.g., a unique ID), and/or metadata associated withthird-party cloud service content item 502. Moreover, in some cases,message 734 can include an ID associated with third-party cloud servicecontent item 502 that content management system 110 can use to identifythird-party cloud service content item 502 and associate message 734with third-party cloud service content item 502.

Content management system 110 can send response 736, which can include,for example, authentication information, such as an authenticationtoken, that third-party cloud service 302 can use to authenticate withcontent management system 110 to provide data or updates associated withthird-party cloud service content item 502. In some cases, response 736can include other information, such as a unique ID, a title ofthird-party cloud service content item 502, access permissionsassociated with third-party cloud service content item 502, metadataassociated with third-party cloud service content item 502, updatesavailable at content management system 110, and so forth.

Third-party cloud service 302 can receive response 736, verifypermissions associated with third-party cloud service content item 502and/or associated data, and send updates 738 to content managementsystem 110 and/or cloud content integration element 702. In someexamples, updates 738 can include authentication information (e.g., anauthentication token) for authenticating with content management system110, updated content associated with third-party cloud service contentitem 502, and/or metadata associated with third-party cloud servicecontent item 502. Content management system 110 can use the informationin updates 738 to modify or update information associated withthird-party cloud service content item 502 and/or smart pointer 504. Forexample, content management system 110 can use the information inupdates 738 to store, modify, present, and/or update metadata or events(e.g., comments, document information, access information orpermissions, content descriptions, user activity, tasks, messages,timestamps, notifications, modifications, etc.) and/or content stored atcontent management system 110 and/or client device 150 for third-partycloud service content item 502 and/or smart pointer 504.

Similarly, cloud content integration element 702 can use the informationin updates 738 to update the content and/or metadata associated with thecopy or representation of third-party cloud service content item 502rendered or presented on client device 150. For example, cloud contentintegration element 702 can use the information in updates 738 to updatethe content presented by interface 620 and/or the features orfunctionalities provided at interface 620 for third-party cloud servicecontent item 502.

If any changes are made at client device 150 to content or metadataassociated with third-party cloud service content item 502, cloudcontent integration element 702 can send updates 740 to contentmanagement system 110 and/or third-party cloud service 302 to propagateor implement such changes on the content management system 110 and/orthird-party cloud service 302. For example, if the user at client device150 adds a comment to the content rendered by interface 620 or executesa content operation such as a rename or edit associated with third-partycloud service content item 502, cloud content integration element 702can provide the added comment or content operation (and/or associatedchanges) to content management system 110 and/or third-party cloudservice 302 for storage and updating of such information pertaining tothird-party cloud service content item 502. To illustrate, cloud contentintegration element 702 can send third-party cloud service 302 updates740 including changes to content in third-party cloud service contentitem 502 made by a user via interface 620 during a presentation ofthird-party cloud service content item 502 at client device 150.

Third-party cloud service 302 can receive updates 740 from cloud contentintegration element 702 and implement such changes on third-party cloudservice content item 502 at third-party cloud service 302. This allowsthe user to interact with a rendered version of third-party cloudservice content item 502 on client device 150, make changes to thecontent, and utilize the various features or functionalities ofthird-party cloud service content item 502, without creating conflictingversions of third-party cloud service content item 502 or otherwiseensuring that any changes implemented on client device 150 arereconciled with a current copy or version of third-party cloud servicecontent item 502 on third-party cloud service 302 and/or any copies orversions of third-party cloud service content item 502 on any otherdevices or locations.

FIG. 7C shows an example process 750 for providing client device 150with the content and third-party cloud service features associated witha cloud-based or cloud-backed content item represented by canonicalcontent item 520 on content management system 110. In this example,canonical content item 520 is stored in user account 704 on contentmanagement system 110. User account 704 can be a user account registeredon content management system 110, which contains content items storedand maintained by the user on content management system 110. In somecases, the content items, including canonical content item 520, in useraccount 704 can also be stored and synchronized locally on client device150 as previously explained. Thus, while canonical content item 520 isdepicted in FIG. 7C as being stored in content management system 110, inother examples canonical content item 520 may also be stored andaccessed locally on client device 150, as shown in FIG. 7D.

In process 750, browser application 166 on client device 150 first sendsrequest 752 to content management system 110 for the content andfeatures of canonical content item 520. Content management system 110can receive request 752 and send response 754 to browser application166, which browser application 166 can use to continue with process 750to render/present the content and features of canonical content item 520on client device 150. Response 754 can include, for example, contentand/or metadata associated with canonical content item 520, whichbrowser application 166 can use to present or render the content andthird-party cloud service 302 features of canonical content item 520.

For example, response 754 can include an ID that can be used to requestmetadata of canonical content item 520 from third-party cloud service302, authentication information (e.g., an authentication token) that canbe used to authenticate third-party cloud service 302 with contentmanagement system 110 to allow the flow of data (e.g., metadata,updates, etc.) and/or communications between content management system110 and third-party cloud service 302, a title identifying canonicalcontent item 520 (and/or its associated cloud-based or cloud-backedcontent item such as third-party cloud service content item 502), accesscontrol permissions configured for user account 704 that define thelevel of access to the content of canonical content item 520 configuredfor user account 704, an address or resource identifier for requestingor obtaining content associated with canonical content item 520 fromthird-party cloud service 302, and/or any other information or metadataassociated with canonical content item 520.

Browser application 166 can receive response 754 from content managementsystem 110 and send, via cloud content integration element 702, request756 to third-party cloud service 302 for metadata associated withcanonical content item 520. Cloud content integration element 702 can beconfigured to send and/or receive calls or requests for data andinformation associated with canonical content item 520 to and/or fromthird-party cloud service 302. The metadata associated with canonicalcontent item 520 can include information used to provide canonicalcontent item 520 one or more features or functionalities enabled orsupported by third-party cloud service 302, such as live collaboration(e.g., commenting, editing, authoring, messaging, etc.) features,previewing functionality, search functionality, indexing functionality,etc.

As previously noted, cloud content integration element 702 can sendrequest 756 to third-party cloud service 302 for data and informationassociated with canonical content item 520. Request 756 can include, forexample, an ID uniquely identifying canonical content item 520 (and/or acloud-based or cloud-backed content item at third-party cloud service302 such as third-party cloud service content item 502), authenticationinformation (e.g., a token for third-party cloud service 302 to use toauthenticate with content management system 110), a title identifyingcanonical content item 520, access control information indicating alevel of access to content associated with canonical content item 520defined for user account 704 and/or client device 150, metadataassociated with canonical content item 520 and/or user account 704,and/or any other information associated with canonical content item 520and/or user account 704.

Cloud content integration element 702 can receive response 758 fromthird-party cloud service 302. Response 758 can include data associatedwith canonical content item 520, such as metadata (e.g., comments,preview(s), indexable content, state information, descriptioninformation, access information, status or activity information, userinformation, etc.) associated with canonical content item 520, and/orany other data.

Cloud content integration element 702 and browser application 166 canuse the data in response 758 to render 760 canonical content item 520(including its associated content and features) in browser application166. At this point, a user at client device 150 can view, access andinteract with the content and features of canonical content item 520from browser application 166. The user can read the content of canonicalcontent item 520, modify the content, add content, add or modifymetadata (e.g., comments, etc.), and otherwise interact with the contentand rendering of canonical content item 520 from browser application 166in a similar fashion as when the user accesses third-party cloud servicecontent item 502 directly from third-party cloud service 302 through acloud-based application or editor (e.g., 604) provided for third-partycloud service content item 502.

In some cases, cloud content integration element 702 can also send orreceive updates 762 to or from third-party cloud service 302 associatedwith canonical content item 520. Updates 762 can include changes and/orinformation associated with canonical content item 520, such as contentor content changes (e.g., rename operations, edit or write operations,delete operations, purge operations, move operations, restoreoperations, revert operations, add or create operations, etc.), metadataor events (e.g., comments, title information or changes, IDs or IDchanges, access information or permissions, organization or storinginformation, membership information, sharing information, userinformation, user activity information, tasks, timestamps, completedtasks or items, etc.), a token to authenticate third-party cloud service302 with content management system 110, and so forth. In some examples,cloud content integration element 702 can receive updates 762 fromthird-party cloud service 302 and implement such updates in the renderedcanonical content item 520 on browser application 166, canonical contentitem 520, and/or user account 704.

In some cases, content management system 110 can similarly send orreceive updates 762 to or from third-party cloud service 302. Contentmanagement system 110 can, for example, send updates 762 when it detectschanges to content or metadata associated with canonical content item520 and can receive updates 762 when content or metadata associated withcanonical content item 520 are modified at third-party cloud service302. Content management system 110 can implement any changes to contentor metadata received in updates 762 from third-party cloud service 302.For example, content management system 110 can update metadataassociated with canonical content item 520, such as comments, state,access information, storage information, or other information, based onupdates 762 received from third-party cloud service 302. In cases wherecanonical content item 520 and third-party cloud service content item502 represent versions of the same content item, updates 762 cansynchronize or harmonize information associated with third-party cloudservice content item 502 on third-party cloud service 302 and canonicalcontent item 520 on content management system 110.

FIG. 7D shows an example process 770 for providing client device 150access to the content and third-party cloud service 302 functionalitiesassociated with canonical content item 502 through canonical contentitem 520 and client application 152 on client device 150. In thisexample, canonical content item 520 is stored on client device 150 alongwith other content items in user account 704 registered on contentmanagement system 110. Process 770 allows a user to store and access thecontent and features of third-party cloud service content item 502 fromclient application 152 (via canonical content item 520) without use ofan application, such as a cloud-based application or editor, designed tonatively support third-party cloud service content item 502. In somecases, the content of canonical content item 520 can be stored oncontent management system 110 and client device 150, but somecloud-based functionalities are obtained from, and provided by,third-party cloud service 302.

In this example, client application 152 invokes 772 canonical contentitem 520 on client device 150, and sends request 774 to contentmanagement system 110 for authentication information associated withcanonical content item 520 (and/or an associated cloud-based orcloud-backed content item such as third-party cloud service content item502). Request 774 can include a unique identifier associated withcanonical content item 520 (and/or third-party cloud service contentitem 502), as well as other information such as a title, user accountinformation, login information, metadata, etc. Content management system110 can receive request 774, verify permissions and/or authentication,and send response 776 to client application 152. Response 776 caninclude authentication information, such as an authentication tokenwhich third-party cloud service 302 can obtain and use to authenticatewith content management system 110 to send, receive, and/or requestmetadata associated canonical content item 520.

It should be noted that in some examples, client application 152 mayskip the process of sending request 774 to content management system 110and receiving response 776, and instead perform the remaining steps inprocess 770 without first sending request 774 and receiving response776. For example, client application 152 may already have anauthentication token or cached authentication information available andthus may not have to send request 774 to content management system 110.In some cases, client application 152 may send request 774 to contentmanagement system 110 if it determines it does not already have anauthentication token or other authentication information, or if anexisting authentication token or authentication information has expired,is invalid, or otherwise should be refreshed, updated, or replaced.

Client application 152 can implement or execute cloud contentintegration element 702 to communicate with third-party cloud service302 as previously described. Here, cloud content integration element 702can use the information in response 776, such as an authenticationtoken, a unique identifier, access control information, a title, etc.,to send request 778 to third-party cloud service 302 for metadataassociated with canonical content item 520. The metadata can includedata for providing cloud-based functionalities to canonical content item520, such as metadata for providing collaboration features (e.g., liveediting, commenting, messaging, authoring, etc.), previewing features,indexing features, search features, etc. Request 778 can include, forexample, authentication information and an ID that third-party cloudservice 302 can use to authenticate, identify and retrieve contentand/or metadata associated with canonical content item 520, and send thecontent and/or metadata to cloud content integration element 702.

Cloud content integration element 702 can receive response 780 sent bythird-party cloud service 302. Response 780 can include metadataassociated with canonical content item 520, content in third-party cloudservice content item 502, a token or authentication information toauthenticate with content management system 110, etc. Client application152 and/or cloud content integration element 702 can use the metadataand information in response 780 to render 782 canonical content item 520and its associated content on interface 620 at client device 150, andprovide support for any features or functionalities associated withthird-party cloud service 302.

At this point, the user at client device 150 can access and interactwith the content and features of canonical content item 520 frominterface 620 on client device 150. In some cases, process 770 caninclude steps for exchanging updates and other information between cloudcontent integration element 702, content management system 110, and/orthird-party cloud service 302. For example, if third-party cloud service302 has updates associated with canonical content item 520, such ascomments, content changes, metadata changes, etc., third-party cloudservice 302 can send message 784 including or requesting authenticationinformation for authenticating with content management system 110 toprovide such updates from third-party cloud service 302. In some cases,message 784 can include authentication information (e.g., a token),identification information (e.g., a unique ID), and/or metadataassociated with canonical content item 520. Moreover, in some cases,message 784 can include an ID associated with canonical content item 520that content management system 110 can use to identify canonical contentitem 520 and associate message 784 with canonical content item 520.

Content management system 110 can send response 786, which can include,for example, authentication information, such as an authenticationtoken, that third-party cloud service 302 can use to authenticate withcontent management system 110 to provide data or updates associated withcanonical content item 520. In some cases, response 786 can includeother information, such as a unique ID, a title of canonical contentitem 520, access permissions associated with canonical content item 520,metadata associated with canonical content item 520, updates availableat content management system 110, and so forth.

Third-party cloud service 302 can receive response 786, verifypermissions associated with canonical content item 520 and/or associateddata, and send updates 788 to content management system 110 and/or cloudcontent integration element 702. In some examples, updates 788 caninclude authentication information (e.g., an authentication token) forauthenticating with content management system 110, updated contentassociated with canonical content item 520, and/or metadata associatedwith canonical content item 520. Content management system 110 can usethe information in updates 788 to modify or update informationassociated with canonical content item 520. For example, contentmanagement system 110 can use the information in updates 788 to store,modify, present, and/or update metadata or events (e.g., comments,document information, access information or permissions, contentdescriptions, user activity, tasks, messages, timestamps, notifications,modifications, etc.) and/or content stored at content management system110 and/or client device 150 for canonical content item 520.

Similarly, cloud content integration element 702 can use the informationin updates 788 to update the content and/or metadata associated with thecontent and/or features rendered or presented on client device 150 forcanonical content item 520. For example, cloud content integrationelement 702 can use the information in updates 788 to update the contentpresented by interface 620 and/or the features or functionalitiesprovided at interface 620 for canonical content item 520.

In some cases, if any changes are made at client device 150 to contentor metadata associated with canonical content item 520, cloud contentintegration element 702 can send updates 790 to content managementsystem 110 and/or third-party cloud service 302 to propagate orimplement such changes on the content management system 110 and/orthird-party cloud service 302. For example, if the user at client device150 adds a comment to the content rendered by interface 620 or executesa content operation such as a rename or edit associated with canonicalcontent item 520, cloud content integration element 702 can provide theadded comment or content operation (and/or associated changes) tocontent management system 110 and/or third-party cloud service 302 forstorage and updating of such information pertaining to canonical contentitem 520 and/or an associated cloud-based or cloud-backed content itemon third-party cloud service 302, such as third-party cloud servicecontent item 502. To illustrate, cloud content integration element 702can send third-party cloud service 302 updates 790 including changes tocontent in canonical content item 520 made by a user via interface 620during a presentation of canonical content item 520 at client device150.

In some cases, if third-party cloud service 302 maintains a copy of acontent item associated with canonical content item 520, such asthird-party cloud service content item 502, third-party cloud service302 can receive updates 790 from cloud content integration element 702and implement such changes on the content item (e.g., third-party cloudservice content item 502) at third-party cloud service 302. This allowsthe user to interact with a rendered version of the content item (e.g.,third-party cloud service content item 502) on client device 150, makechanges to the content, and utilize the various features orfunctionalities of the content item (e.g., third-party cloud servicecontent item 502), without creating conflicting versions of the contentitem (e.g., third-party cloud service content item 502) or otherwiseensuring that any changes implemented on client device 150 arereconciled with a current copy or version of the content item (e.g.,third-party cloud service content item 502) on third-party cloud service302 and/or any copies or versions of the content item on any otherdevices or locations.

FIG. 8 shows an example flow (800) for exchanging data (e.g., content,metadata, etc.) and updates associated with a cloud-based orcloud-backed content item, such as canonical content item 520 orthird-party cloud service content item 502, between content managementsystem 110 and third-party cloud service 302. In this example, contentmanagement system 110 sends request 802 to third-party cloud service 302for data (e.g., metadata, content, etc.) associated with a cloud-basedor cloud-backed content item (e.g., canonical content item 520,third-party cloud service content item 502, etc.). Request 802 caninclude authentication information, a request for data associated withthe content item, an ID associated with the cloud-based or cloud-backedcontent item, and/or other information associated with the cloud-basedor cloud-backed content item such as a title, access permissions,sharing information, description information, metadata, etc. Third-partycloud service 302 receives request 802, verifies permissions and/oraccess to the cloud-based or cloud-backed content item, and sendsresponse 804 to content management system 110. Response 804 can includethe content in the cloud-based or cloud-backed content item and/or anymetadata associated with the cloud-based or cloud-backed content item.

In some examples, response 804 can include authentication information(e.g., an authentication token) for authenticating with contentmanagement system 110 and/or data (e.g., content, metadata, etc.)associated with the cloud-based or cloud-backed content item. Contentmanagement system 110 can store the information in response 804 and/oruse the information to create or store a preview of the cloud-based orcloud-backed content item, create or store a canonical content item(e.g., 520) corresponding to the cloud-based or cloud-backed contentitem, create or store a smart pointer (e.g., 504) corresponding to thecloud-based or cloud-backed content item, store or update metadataassociated with the cloud-based or cloud-backed content item and/or acanonical content item or smart pointer corresponding to the cloud-basedor cloud-backed content item, store the content of the cloud-based orcloud-backed content item, provide the content of the cloud-based orcloud-backed content item to one or more client devices for presentationor access, configure attributes (e.g., storage organization, accesscontrol permissions, content features, functionalities, etc.) associatedwith the cloud-based or cloud-backed content item or an associatedcanonical content item or smart pointer, extend the features orfunctionalities available for the cloud-based or cloud-backed contentitem based on features or functionalities provided by content managementsystem 110, etc.

If third-party cloud service 302 detects any changes in the content ormetadata of the cloud-based or cloud-backed content item, it can sendupdates 806 to content management system 110 to inform contentmanagement system 110 of such changes. Content management system 110 canuse the information in updates 806 to perform update 808 at contentmanagement system 110. Content management system 110 can perform update808 to implement any changes included in updates 806 or updateassociated information on content management system 110.

Similarly, if content management system 110 detects any changes in thecontent or metadata of the cloud-based or cloud-backed content itemand/or an associated canonical content item (e.g., 520) or smart pointer(e.g., 504), it can send updates 810 to third-party cloud service 302 toinform third-party cloud service 302 of such changes. Third-party cloudservice 302 can use the information in updates 810 to perform update 812at third-party cloud service 302. Third-party cloud service 302 canperform update 812 to implement any changes included in updates 810 on acopy of the cloud-based or cloud-backed content item at third-partycloud service 302.

FIG. 9A shows an example flow (900) for creating associations betweencontent and metadata in third-party cloud service content item 502 onthird-party cloud service 302 and smart pointer 504 in contentmanagement system 110. In flow 900, content management system 110 canreceive data from third-party cloud service 302 that content managementsystem 110 can use to associate smart pointer 504 (and any of itsassociated content or metadata) with third-party cloud service contentitem 502 and third-party cloud service 302, and store or createassociated content or metadata for smart pointer 504, such as indexablecontent 506A, previews 506B, comments 506N, etc. Content managementsystem 110 can also use the received data to do functionality mappings(e.g., 500) as previously described with respect to FIG. 5A.

In flow 900, content management system 110 sends message 902 withauthentication information to third-party cloud service 302 in order toenable the exchange of data associated with third-party cloud servicecontent item 502. Message 902 can include, for example, anauthentication token as well as other information associated withthird-party cloud service content item 502, such as a unique ID, atitle, access control information, etc. Message 902 can request data orinformation associated with third-party cloud service content item 502from third-party cloud service 302.

Third-party cloud service 302 can receive message 902, authenticate withcontent management system 110, verify access to third-party cloudservice content item 502 and/or its associated data, and/or sendassociated data 904 to content management system 110. Associated data904 can include content, metadata, and/or information associated withthird-party cloud service content item 502, which content managementsystem 110 can use to create, store, and/or associate content or datawith smart pointer 504.

For example, associated data 904 can include indexable content 506Aassociated with third-party cloud service content item 502, whichcontent management system 110 can use for indexing and to provide searchfunctionality for smart pointer 504. Since content management system 110may not store the actual content of third-party cloud service contentitem 502 in smart pointer 504 (or elsewhere in content management system110), content management system 110 may not otherwise have contentassociated with third-party cloud service content item 502 available forindexing and searching. Thus, content management system 110 can receiveindexable content 506A (e.g., via associated data 904) from third-partycloud service 302 and use indexable content 506A for indexing and searchfunctionalities.

In some cases, associated data 904 can include one or more previews 506Bof third-party cloud service content item 502 and/or content thatcontent management system 110 can use to create previews 506B for smartpointer 504. Content management system 110 can store previews 506B foraccess by users. Previews 506B can be used to render a preview of smartpointer 504 (or the content associated with smart pointer 504 andthird-party cloud service content item 502).

In some examples, associated data 904 can include comments 506Nassociated with third-party cloud service content item 502 and/orcontent within third-party cloud service content item 502. Contentmanagement system 110 can associate comments 506N with smart pointer 504and/or one or more portions of content associated with smart pointer504, and store comments 506N for access by users interacting with smartpointer 504. In some cases, content management system 110 can providecomments 506N as notifications to users or may embed comments 506N insmart pointer 504 (or its associated content) or otherwise providecomments 206N along with smart pointer 504 when rendered or presented toa user.

In some cases, comments 506N can be anchored or unanchored. Anchoredcomments can refer to comments that are mapped or anchored to specificcontent in a content item (e.g., smart pointer 504) and unanchoredcomments can refer to comments that are not mapped or anchored tospecific content in a content item (e.g., smart pointer 504) but rathermapped to or associated with the content item as a whole. For example, acomment may be specific to a paragraph in a content item (e.g., smartpointer 504). Accordingly, the comment can be mapped to or associatedwith that particular paragraph. Once mapped to or associated with theparticular paragraph, the comment becomes an anchored comment as it isspecifically anchored to the paragraph it pertains to.

However, in some cases, content management system 110 may not haveenough information to determine which specific portion(s) of contentwithin a content item a comment pertains to. Accordingly, contentmanagement system 110 may not be able to anchor the comment to anyspecific portion(s) of the document or file, and instead maps orassociates the comment with the content item as a whole. For example,content management system 110 may have a comment received fromthird-party cloud service 302 for third-party cloud service content item502, but may not have information identifying which specific portion(s)of content within third-party cloud service content item 502 the commentpertains to. As a result, content management system 110 may not be ableto map or anchor the comment to a specific portion(s) of the content inthird-party cloud service content item 502. Instead, content managementsystem 110 may associate the comment with third-party cloud servicecontent item 502 (and/or smart pointer 504) as a whole.

As illustrated in flow 900, associated data 904 received fromthird-party cloud service 302 can be used by content management system110 to create associations between smart pointer 504 and content ormetadata corresponding to smart pointer 504. Such associations canenable content management system 110 to provide or support variousfeatures and functionalities for smart pointer 504 and, in some cases,extend the features or functionalities of smart pointer 504 to includeother features or functionalities made available through the ecosystemof content management system 110 and its own supported content, storage,collaboration, interaction, and other features and functionalities.

FIG. 9B shows an example flow (920) for creating associations betweencontent and metadata in third-party cloud service content item 502 onthird-party cloud service 302 and canonical content item 520 in contentmanagement system 110. In flow 920, content management system 110 canreceive data from third-party cloud service 302 that content managementsystem 110 can use to associate canonical content item 520 (and any ofits associated content or metadata) with third-party cloud servicecontent item 502 and third-party cloud service 302, and store or createassociated content or metadata for canonical content item 520, such asindexable content 526A, previews 526B, comments 526N, etc. Contentmanagement system 110 can also use the received data to do functionalitymappings (e.g., 524) as previously described with respect to FIG. 5B.

In flow 920, content management system 110 sends message 922 withauthentication information to third-party cloud service 302 in order toenable the exchange of data associated with third-party cloud servicecontent item 502. Message 922 can include, for example, anauthentication token as well as other information associated withthird-party cloud service content item 502, such as a unique ID, atitle, access control information, etc. Message 922 can request data orinformation associated with canonical content item 520 and third-partycloud service content item 502 from third-party cloud service 302.

Third-party cloud service 302 can receive message 922, authenticate withcontent management system 110, verify access to the data and/or featuresassociated with third-party cloud service content item 502, and/or sendassociated data 924 to content management system 110. Associated data924 can include data (e.g., metadata, content, etc.) and/or informationassociated with third-party cloud service content item 502 and canonicalcontent item 520, which content management system 110 can use to create,store, and/or associate data with canonical content item 520. Forexample, associated data 924 can include indexable content 526A thatcontent management system 110 can use for indexing and to provide searchfunctionality for canonical content item 520.

In some cases, associated data 924 can include one or more previews 526Bthat content management system 110 can use to create previews 526B forcanonical content item 520. Content management system 110 can storepreviews 526B for access by users. Previews 526B can be used to render apreview of canonical content item 520 (or the content associated withcanonical content item 520). In some examples, associated data 924 caninclude comments 526N associated with canonical content item 520 and/orthird-party cloud service content item 502. Content management system110 can associate comments 526N with canonical content item 520 and/orone or more portions of content associated with canonical content item520, and store comments 526N for access by users interacting withcanonical content item 520. In some cases, content management system 110can provide comments 526N as notifications to users or may embedcomments 526N in canonical content item 520 (or its associated content)or otherwise provide comments 206N along with canonical content item 520when rendered or presented to a user.

As previously explained, in some cases, comments 526N can be anchored orunanchored. Anchored comments can refer to comments that are mapped oranchored to specific content in a content item (e.g., canonical contentitem 520) and unanchored comments can refer to comments that are notmapped or anchored to specific content in a content item (e.g.,canonical content item 520) but rather mapped to or associated with thecontent item as a whole.

As illustrated in flow 920, associated data 924 received fromthird-party cloud service 302 can be used by content management system110 to create associations between canonical content item 520 andcontent or metadata corresponding to canonical content item 520 (andthird-party cloud service content item 502). Such associations canenable content management system 110 to provide or support variousfeatures and functionalities for canonical content item 520 and, in somecases, extend the features or functionalities of canonical content item520 to include other features or functionalities made available throughthe ecosystem of content management system 110 and its own supportedcontent, storage, collaboration, interaction, and other features andfunctionalities.

FIG. 10 shows flow 1000 for pushing to third-party cloud service 302local changes made to smart pointer 504 and/or canonical content item520 on client device 150. In this example, third-party cloud servicecontent item 502A is a cloud-based or cloud-backed content itemassociated with smart pointer 504, and third-party cloud service contentitem 502B is a version of a cloud-based or cloud-backed content itemrepresented by canonical content item 520.

In flow 1000, when client device 150 executes operation 1002 resultingin changes to the content and/or metadata of smart pointer 504 and/orcanonical content item 520 (and thus the content and/or metadata inthird-party cloud service content item 502A and/or 502B), it can sendupdates 1006 identifying such changes to content management system 110.Content management system 110 can receive updates 1006 and send them tothird-party cloud service 302. Third-party cloud service 302 can receiveupdates 1006 and use the information in updates 1006 to update 1004third-party cloud service content item 502A (and/or its associatedmetadata) and/or 502B (and/or its associated metadata) to reflect thechanges in updates 1006.

Operation 1002 can include any filesystem operation executed at clientdevice 150 on content or metadata associated with smart pointer 504and/or canonical content item 520 (and thus third-party cloud servicecontent item 502A and/or 502B). Non-limiting examples of operation 1002include a rename operation, a copy operation, a delete operation, anedit or write operation, a restore operation, an operation for revertingto a previous version of content, etc. Flow 1000 allows any localchanges to content or metadata associated with smart pointer 504 and/orcanonical content item 520 resulting from operation 1002 to bepropagated to or synchronized with third-party cloud service contentitem 502A and/or 502B on third-party cloud service 302, so changes madeto the content or metadata from client device 150 are not omitted fromthird-party cloud service content item 502A and/or 502B on third-partycloud service 302 (or any other devices with access to third-party cloudservice content item 502A and/or 502B) and do not result in conflictingversions or copies on client device 150, content management system 110,and/or third-party cloud service 302, and to provide a uniform orintegrated user and content experience across client device 150, contentmanagement system 110, and third-party cloud service 302.

FIG. 11 shows an example link-based mechanism for sharing cloud-based orcloud-backed content items stored in content management system 110 withusers and devices. In this example, canonical content item 520represents a cloud-based or cloud-backed content item stored in contentmanagement system 110 and being shared with users and devices using theexample link-based mechanism described herein. As shown in FIG. 11,content management system 110 can create links 1102, 1104, 1106 tocanonical content item 520. Links 1102, 1104, 1106 can be used to sharecanonical content item 520 with client devices 150 _(k), 150 ₂, 150 _(N)and/or user accounts A, B, N. Links 1102, 1104, 1106 to canonicalcontent item 520 can be configured with specific permissions so thelinks are pre-configured to provide a specific level of access to linkrecipients (e.g., client devices 150 _(k), 150 ₂, 150 _(N)).

For example, link 1102 can be a link configured to provide read-onlyaccess to canonical content item 520. Thus, when content managementsystem 110 provides link 1102 to client device 150 _(k), the user atclient device 150 ₁ will be able to use link 1002 to view or read thecontent associated with canonical content item 520 but will not be ableto otherwise delete, modify or edit the content. On the other hand, link1104 can be configured to provide edit access or modification rights tocanonical content item 520. Thus, when content management system 110provides link 1104 to client device 150 ₂, the user at client device 150₂ will be able to use link 1104 to view/read and edit/modify the contentassociated with canonical content item 520.

The different links (1102, 1104) with different rights or permissionscan be used to share different levels or types of access with clientdevices in order to provide greater sharing flexibility and granularity.The different links (1102, 1104) also allow access to be revoked fromone link without affecting access through other links. For example, ifcontent management system 110 revokes link 1102, those users and devices(e.g., client device 150 ₂) having link 1104 may not lose access tocanonical content item 520 simply because link 1102 has been revoked.Likewise, if content management system 110 revokes link 1104, thoseusers and devices (e.g., client device 150 ₁) having link 1102 may notlose access to canonical content item 520 simply because link 1104 hasbeen revoked.

Link 1106 is a reference link that does not confer or provide any rightsor permissions to canonical content item 520. Instead, link 1106uniquely identifies canonical content item 520 and can be used torequest access to canonical content item 520. Thus, when contentmanagement system 110 provides link 1106 to client device 150 ₃, theuser at client device 150 ₃ will not be able to access canonical contentitem 520 from link 1106, but will rather be able to use link 1106 torequest access to canonical content item 520.

Link 1106 can also provide a means for users to regain access tocanonical content item 520 when links 1102 or 1104 are revoked. Forexample, if there is a security threat or unauthorized access resultingfrom an unauthorized user gaining access to link 1102, contentmanagement system 110 can revoke link 1102 to prevent unauthorizedaccess to content through link 1102. When content management system 110revokes link 1102, this can cause any users or devices that have aread-only link (e.g., link 1102) to canonical content item 520 to loseaccess to canonical content item 520. For example, when contentmanagement system 110 revokes link 1102, it can retroactively remove theread/view rights or permissions on all read-only links (e.g., 1102) toprevent unauthorized access to canonical content item 520 from anyread-only link shared with users or devices. As a result, those users ordevices with read-only links will lose access to the content.

However, in some cases, when content management system 110 revokes theread-only links (e.g., 1102) or removes the rights/permissions from theread-only links, it can downgrade the read-only links to reference links(e.g., 1106). The reference links (e.g., 1106) then allow those users ordevices losing access as a result of the read-only links being revoked(or their rights/permissions removed) to use the reference links torequest and regain access to canonical content item 520. Therefore,those users or devices will have a means to regain access to canonicalcontent item 520 after the revocation of read-only links or therights/permissions configured for those links.

Similarly, if content management system 110 revokes the edit links(e.g., 1104) or removes the rights/permissions from the edit links, itcan downgrade such links to reference links (e.g., 1106). As previouslyexplained, the reference links (e.g., 1106) allow those users or deviceslosing access as a result of the edit links being revoked (or theirrights/permissions removed) to use the reference links to request andregain access to canonical content item 520. The users or devices willthus have a means to regain access to canonical content item 520 afterthe revocation of the edit links (e.g., 1104) or the rights/permissionsconfigured for those links.

FIG. 12 shows an example flow for routing users working on cloud-backedcontent items to live collaboration sessions. In some cases, a user maywant to open a cloud-backed content item (e.g., canonical content item520, third-party cloud service content item 502, etc.) in an applicationthat does not support collaboration functionalities, is not compatiblewith the collaboration functionality of the cloud-backed content item,or is not configured or activated to obtain additional cloudfunctionalities. However, if there is a live collaboration sessionbetween users interacting and working on the cloud-backed content item,by opening the cloud-backed content item in such application, the userwill not be able to participate in the live collaboration session withsuch users or access the activity and services generated for thecloud-backed content item in the collaboration session. The user willthus have a limited experience and will lose the benefits of thecollaborative experience otherwise available for the cloud-backedcontent item.

The example flow in FIG. 12 allows such a user to be given an option toaccess the cloud-backed content item using the application that does notsupport the collaboration functionalities and an option to be routed toanother application or integration element (e.g., client application 152or browser application 166 configured to employ cloud contentintegration element 702) that does support such collaborationfunctionalities and join the collaboration session.

Starting at step 1202, client device 150 invokes an instance of acloud-backed content item (e.g., canonical content item 520, an instanceof third-party cloud service content item 502, etc.) using a localapplication on client device 150. The local application can be anyapplication or editor on client device 150. For example, the localapplication can be client application 152, browser application 166, acloud-based application or editor (e.g., third-party cloud serviceapplication 604), a native application, or any other type of applicationor editor. In some examples, the local application can be an applicationthat does not support collaboration functionalities, is not compatiblewith the collaboration functionalities of the cloud-backed content item,or is not configured or enabled to obtain such collaborationfunctionalities from a cloud service. In other examples, the localapplication can be a cloud-based application that is compatible with thecloud-backed content item.

At step 1204, the flow involves determining whether there is a livecollaboration session associated with the cloud-backed content item. Thelive collaboration session can include users editing and/or interactingwith the cloud-backed content item in a collaborative manner (e.g., in amanner which allows each user to see changes and activity generated byother users). If there are no live collaboration sessions associatedwith the cloud-backed content item or no other users (e.g., other thanthe user associated with client device 150) currently editing and/orinteracting with the cloud-backed content item with whom client device150 can establish a live collaboration session, the flow can end and theuser may proceed as desired by opening and working on the cloud-backedcontent item using the local application or otherwise abandoning theprocess. On the other hand, if there is a live collaboration sessionassociated with the cloud-backed content item, the flow can proceed tostep 1206.

At step 1206, if there is a live collaboration session associated withthe cloud-backed content item or if there are other users available(e.g., currently editing and/or interacting with the cloud-backedcontent item) to establish a live collaboration session with clientdevice 150 can establish a live collaboration session, the user can begiven an option to join (or establish) the live collaboration session.The user can be notified that a live collaboration session for thecloud-backed content item exists and provided with a prompt or option tojoin the live collaboration session. The prompt or option can include,for example and without limitation, an interface element, a message, ora link that the user can select to join the live collaboration session.

If the user chooses to join the live collaboration session, at step 1208the client device 150 associated with the user can be routed to anapplication, editor, or interface with live collaboration support forthe cloud-backed content item. The user can then join the livecollaboration session using the application, editor or interface thatthe user was routed to. The application, editor or interface can obtainsuch live collaboration functionalities from a cloud service (e.g., 302,304, 306, 170) as previously described.

For example, the client device 150 can be routed to client application152 or browser application 166, which can implement cloud contentintegration element 702 to provide collaboration support for thecloud-backed content item as previously described, and allow the user tojoin the live collaboration session. As another example, the clientdevice 150 can be routed to a cloud-based application or editor, such asthird-party cloud service application 604, that supports collaborationfor the cloud-backed content item and allows the user to join the livecollaboration session.

In some cases, the application or editor a user is routed to at step1208 can depend on one or more factors, such as user preferences,default application or editor settings, the user's current context orexperience (e.g., the user's login status, the user's manner forreceiving the content item such as through in-band sharing, etc.). Forexample, if the user at client device 150 accesses a .docx content itemreceived through in-band sharing (e.g., shared and received throughcontent management system 110) during a desktop or web experience, theuser can be routed to a file viewer application (e.g., an applicationthat presents data or content stored in a content item) if the user hasview permissions for the .docx content item, or the user can be routedto an online or cloud-based editor for .docx content items (e.g., GOOGLEDOCS or MICROSOFT WORD ONLINE) if one is available at client device 150and if the user has edit permissions for the .docx content item.

As another example, if the user accesses a .paper content item sharedthrough in-band sharing during a desktop or web experience, the user canbe routed to DROPBOX PAPER (Web version or desktop version ifavailable), which supports .paper content items; and if the useraccesses a .gdoc content item received through in-band sharing during adesktop or web experience, the user can be routed to GOOGLE DOCS whichsupports .gdoc content items.

In other examples, if the user at client device 150 accesses a .docxcontent item while logged out of an online or cloud-based editor for.docx content items, the user can be routed to a file viewer applicationon client device 150 for view-only access to the .docx content item andgiven an option to sign in to the online or cloud-based editor to obtainedit access to the .docx content item. If the user accesses a .paperfile while logged out of DROPBOX PAPER, the user can be routed toDROPBOX PAPER (Web) with view-only access and given an option to signinto DROPBOX PAPER to obtain edit access to the .paper content item. Ifthe user accesses a .gdoc while logged out of GOOGLE DOCS, the user canbe routed to GOOGLE DOCS with view-only access and given an option tosign into GOOGLE DOCS for edit access to the .gdoc content item.

In some cases, the dynamic routing of the user to a specificapplication, editor, or interface with live collaboration support forthe cloud-backed content item can be triggered not only when a livecollaboration session associated with the cloud-backed content itemexists, but also if such a live collaboration session can be establishedor initiated when client device 150 invokes the instance of thecloud-backed content item at step 1202. For example, if client device150 invokes the cloud-backed content item and another user isalready/currently editing and/or interacting with the cloud-backedcontent item from a different device, the invocation of the cloud-backedcontent item can create an opportunity to establish or initiate a newlive collaboration session between the user associated with clientdevice 150 and the other user editing and/or interacting with thecloud-backed content item. This opportunity to establish or initiate anew live collaboration session can trigger the dynamic routing describedat steps 1206 and 1208. Thus, the user can be given an option to join anew live collaboration session with the other user and can be routed toa specific application, editor or interface with live collaborationsupport if the user chooses to join the new collaboration session.

Moreover, the dynamic routing of the user to a specific application,editor, or interface with live collaboration support for thecloud-backed content item at step 1208 can be triggered when clientdevice 150 invokes an instance of the cloud-backed content item from anylocal application at client device 150. In some examples, the dynamicrouting can be triggered when client device 150 invokes the instance ofthe cloud-backed content item using a local application that does notsupport collaboration functionalities, is not compatible with thecollaboration functionalities of the cloud-backed content item, or isnot configured or enabled to obtain such collaboration functionalitiesfrom a cloud service.

In other examples, the local application can be a cloud-basedapplication that is compatible with the cloud-backed content item. Inother examples, the dynamic routing can be triggered when client device150 invokes the instance of the cloud-backed content item using a localapplication that is different from an application being used by anotheruser to edit and/or interact with the cloud-backed content item onanother device. Here, the user can be routed to (and/or given the optionto be routed to) a different application even if the local applicationis compatible with the cloud-backed content item and/or supportscollaboration functionalities.

If at step 1206 the user chooses not to join the live collaborationsession, the user can be presented with an option to proceed withoutlive collaboration functionalities. In such cases, at step 1210, theuser is provided an option to open the cloud-backed content item fromthe local application without live collaboration functionalities. If theuser at step 1210 chooses to open the cloud-backed content item withoutlive collaboration functionalities, at step 1212 the client device 150can proceed to open the cloud-backed content item in the localapplication without live collaboration functionalities. If the user atstep 1210 instead chooses not to proceed opening the cloud-backedcontent item without live collaboration functionalities, the flow endsand the user can optionally return to step 1202 at any point.

Having disclosed example system components and concepts, the disclosurenow turns to example methods 1300, 1320, 1340 and 1360 for integratingcloud content items with a content management system (110), as shown inFIGS. 13A through 13D. The steps outlined herein are non-limitingexamples provided for illustration purposes, and can be implemented inany combination thereof, including combinations that exclude, add, ormodify certain steps.

At step 1302, method 1300 can include receiving a request to access asmart pointer (e.g., 504) stored at a content management system (e.g.,110). The smart pointer can include a representation of a content item(e.g., third-party cloud service content item 502) stored at a cloudservice (e.g., 302, 304, 306, 170), such as a cloud-backed content itemor a cloud-based content item. The content and features of the contentitem can be accessed through an online application (e.g., third-partycloud service application 604) associated with the cloud service. Theonline application can include, for example, an online or webapplication or editor from the cloud service. Moreover, the onlineapplication can have native support for the content item, including thecontent and features of the content item. In some cases, the content andfeatures of the content item may only be accessible or supported throughthe online application or through a different application using theapproaches described herein.

The smart pointer can be stored at a user account (e.g., 704) registeredat the content management system (110). The user account can include thesmart pointer as well as other content items such as canonical contentitems, basic pointers, traditional content items, folders, images,videos, documents, audio content items, files, collections, and/or anyother type of digital data. In some aspects, the content items on theuser account can be stored on the content management system (110) aswell as one or more client devices (e.g., 150). Moreover, one or more ofthe content items (and/or associated changes) in the user account can besynchronized between the content management system (110) and the one ormore client devices (e.g., 150) in order to maintain a consistent copyof the content items across the content management system (110) and theone or more client devices (e.g., 150).

In some cases, the smart pointer (504) can be stored without the actualcontent of the content item. Instead, the content can be retrieved fromthe cloud service when the smart pointer is invoked or opened asdescribed herein. However, in some cases, the smart pointer (504) mayinclude at least some of the actual content of the content item or maybe stored with the actual content.

Moreover, in some cases, the smart pointer (504) can be stored alongwith other content items on a user account at the content managementsystem and according to a filesystem storage scheme or otherorganization scheme for storing the smart pointer and any other contentitems on the user account. For example, the smart pointer can be storedwith other content items in a hierarchical file system or storagescheme, and visually depicted in storage as a content item such as afile or document. Thus, the content management system (110) can provideaccess control and organization for the smart pointer as well as anyother content items on the user account.

At step 1304, method 1300 can include, in response to the smart pointer(504) being invoked, sending, from a cloud content integration element(e.g., 602) on a local application (e.g., client application 152 orbrowser application 166) to the cloud service (e.g., 302, 304, 306, or170), a request (e.g., 710, 728, 802) for the content of the contentitem (e.g., 502) associated with the smart pointer (504). In someexamples, the request for the content can include a unique ID associatedwith the smart pointer, the content and/or the content item;authentication information; a title of the content item; access controlpermissions configured at the content management system (110) for thesmart pointer, the content, and/or the content item; etc. The accesscontrol permissions can correspond to a user account (e.g., 704) that isassociated with the request for the content and registered at thecontent management system (110).

In some aspects, the local application may not provide native supportfor the content item, the content in the content item, and/or featuresor functionalities associated with the content item. Instead, the localapplication may implement the cloud content integration element (e.g.,602) to provide support for the content item, the content in the contentitem, and/or features or functionalities associated with the contentitem. The features or functionalities can include one or more featuresor functionalities provided by the cloud service and accessible throughthe online application (e.g., 604) associated with the cloud service.Non-limiting examples of features or functionalities associated with thecontent item can include commenting, notifications, bi-directionalcommunications or interactions between users working on the contentitem, live editing or collaboration sessions, tasks, editing, sharing,activity feeds, content or metadata updates, etc.

At step 1306, method 1300 can include receiving, at the cloud contentintegration element (e.g., 602) on the local application (e.g., 152 or166) and from the cloud service (e.g., 302, 304, 306, or 170), thecontent of the content item (e.g., 502) associated with the smartpointer. In some cases, the cloud content integration element (e.g.,602) can also receive other content or data associated with the contentitem, such as indexable content, a content or document preview, metadata(e.g., comments, tasks, state, events, updates, user activityinformation, status information, etc.), and/or any other data orinformation associated with the content item.

At step 1308, method 1300 can include, in response to receiving thecontent of the content item (e.g., 502), presenting, on the localapplication (e.g., 152 or 166), the content of the content item as partof a rendered instance (e.g., 602) of the smart pointer (504). Thecontent can be presented within the rendered instance of the smartpointer so as to mirror or resemble the content item on the cloudservice when rendered or displayed for a user. In some examples, therendered instance of the smart pointer can be presented along with thecontent without translating the content prior to presentation of thecontent. In other words, the local application can have the capabilityto render the content without first having to modify the configurationand/or format of the content to a different configuration and/or formatsupported by the local application. Thus, the local application maysupport the configuration and/or format of the content. In otherexamples, the local application may instead modify the configurationand/or format of the content prior to rendering, in order to prepare orenable the content for rendering by the local application.

Moreover, the cloud content integration element (e.g., 602) on the localapplication and/or the content management system (110) can allow data(e.g., content, metadata, events, etc.) added or modified on the contentitem in the cloud service to be implemented on the smart pointer (504)and vice versa. For example, if a user renames the content item on thecloud service, the cloud service can provide the change to the contentitem associated with the smart pointer (504) by sending an update to thecloud content integration element (e.g., 602) and/or the contentmanagement system (110). When the cloud content integration element(e.g., 602) and/or the content management system (110) receives theupdate from the cloud service, the cloud content integration element(e.g., 602) and/or the content management system (110) can rename thesmart pointer (504) accordingly to match the renaming of the contentitem.

The cloud content integration element (e.g., 602) and/or the contentmanagement system (110) can also enable collaborative functionalitiesand live editing or collaboration sessions between users working on thesmart pointer (504) and the content item on the cloud service. Forexample, the cloud content integration element (e.g., 602) and/or thecontent management system (110) can communicate with the cloud serviceto exchange information and communications, thereby providing supportfor bi-directional or two-way communications between the smart pointer(504) and the content item on the cloud service.

To illustrate, comments or messages created from, or added to, thecontent item on the cloud service can be propagated to the smart pointer(e.g., via the cloud content integration element and/or the contentmanagement system) so a user working on the smart pointer (504) can viewor interact with the comments or messages created from, or added to, thecontent item and received from the cloud service, and vice versa. A userworking on the smart pointer (504) can receive or view the comments ormessages from the rendered instance of the smart pointer and reply tothe comments or messages from the smart pointer. Any replies added bythe user from the smart pointer can be similarly propagated to thecontent item on the cloud service so any users working on the contentitem can receive and view such replies. Such collaborations andinteractions between users can be exchanged and implemented between thesmart pointer and the content item hosted by the cloud service toprovide an integrated, collaborative experience across all platforms(e.g., the content management system, the local application, the cloudservice, etc.).

In some aspects, the local application can perform filesystem operations(e.g., 1002) and/or other file or content operations on the canonicalcontent item, such as copy operations, move operations, createoperations, delete operations, purge operations, restore operations,rename operations, version history operations, sharing operations, etc.The local application can propagate any changes resulting from suchoperations to the content item on the cloud service. For example, thelocal application can implement the cloud content integration element(e.g., 602) to send updates (e.g., 716, 740, 1006) to the cloud servicewith the changes from the operations, which the cloud service can use toupdate the content item on the cloud service. The changes can include,for example, changes to the content item, changes to metadata of thecontent item, changes to the content of the content item, changes to thesmart pointer, etc.

In some cases, method 1300 can include receiving, at the cloud contentintegration element (e.g., 602) on the local application and from thecloud service, metadata identifying a comment added to the content item(e.g., 502) stored on the cloud service, and presenting, on the localapplication, the comment with the rendered instance of the smartpointer. The comment can be a comment added by a remote user working onthe content item from the cloud service or a remote user working on arendered instance of another copy of the smart pointer. Moreover, thecomment can be presented within the rendered instance of the smartpointer, within a separate user interface or application, or within amessage or notification to the user of the local application. Thus, auser viewing or working on the rendered instance of the smart pointercan receive or view comments added to the content item by other usersand thereby obtain a collaborative experience when accessing or workingon the rendered instance of the smart pointer.

In some cases, the local application can receive one or more commentsadded to the rendered instance of the smart pointer from the localapplication and propagate the one or more comments to the cloud servicefor inclusion or implementation in the content item on the cloudservice. For example, when the local application receives a commentadded by a user working with the rendered instance of the smart pointerat the local application, it can use the cloud content integrationelement (e.g., 602) to send an update message (e.g., 716, 740) to thecloud service. The update message can identify the comment added by theuser to the rendered instance of the smart pointer. The cloud servicecan receive the update message and apply or add the comment from theupdate message to the content item on the cloud service. This way,comments added to the content item on the cloud service and commentsadded to the rendered instance of the smart pointer can be exchangedbetween the local application and the cloud service to provide acollaborative experience and maintain consistency between the contentitem on the cloud service and the smart pointer.

In some cases, the cloud content integration element (e.g., 602) on thelocal application can receive, from the cloud service, data associatedwith the content item, such as metadata (e.g., comments, activity,events, tasks, content item information, update information, etc.)associated with the content item, one or more previews (e.g., a contentitem preview such as a text or image preview), indexable content (e.g.,text, image, and/or other digital content that can be indexed forsearching) corresponding to the content item, etc. The data from thecloud service can be presented by the local application as part of therendered instance of the smart pointer, displayed on a separateinterface, presented on a message or notification, depicted in storage(e.g., as a file or document in storage), etc.

Moreover, in some cases, the data or portions of the data can be indexedfor searching. For example, the local application can receive a searchrequest from a user which includes a query for a portion of the dataand, in response to the search request, the local application can searchany indexed data on the user account (e.g., 704) for the portion of thedata associated with the search request. The local application can thenpresent a search result to the user including any matches or, if nomatches are found, an indication that no matches were found.

In some cases, the data associated with the content item can include apreview of the content item and/or an indication of user activityassociated with the content item. The user activity can include anyinteractions between a user(s) and the content item, any eventsgenerated by a user(s) working on the content item, etc. The preview caninclude, for example, a preview (e.g., an image preview, a text preview,a file preview, etc.) of the content item or one or more portions ofcontent in the content item.

The local application can present the preview and/or the user activityto a user having access to the smart pointer or viewing/working on therendered instance of the smart pointer. For example, the localapplication can display an activity feed or activity notificationidentifying the user activity. In some examples, the preview can bestored in the user account (e.g., 704) and depicted as a content item instorage. The user can view the preview from storage without having toaccess the content item or obtain a rendered instance of the smartpointer. Moreover, the preview can be used by the user's device (e.g.,150) or the content management system (110) to search for contentassociated with the content item.

In some cases, method 1300 can include receiving a request to open acopy of a specific content item (e.g., a specific cloud-backed contentitem, a specific cloud-based content item, etc.) using a specificapplication that is different from an online application or editor thatis associated with the specific content item and provides native supportfor the specific content item and its associated content andfeatures/functionalities. Method 1300 can further include identifying alive collaboration session between users interacting with the specificcontent item (e.g., via respective client devices) and determining thatthe specific application does not support live collaboration for thecopy of the specific content item. Method 1300 can also includeproviding a prompt to the requesting user or device with an option tojoin the live collaboration session via a different application thatsupports live collaboration for the specific content item, and inresponse to receiving an acceptance of the option to join the livecollaboration session, routing the requesting user or device to thedifferent application and/or joining the requesting user or device tothe live collaboration session via the different application.

In some cases, method 1300 can also include generating a plurality ofsharing links to the smart pointer (504). The sharing links can beconfigured with various access rights, and the sharing links can be usedto share the smart pointer with users and provide such users a specificlevel of access to the smart pointer. For example, the plurality ofsharing links can include a view link (e.g., 1102) configured withread-only access rights to the smart pointer (504), an edit link (e.g.,1104) configured with edit access rights to the smart pointer (504),and/or a reference link (e.g., 1106) that uniquely identifies the smartpointer (504) and confers no access rights to the smart pointer (504).Method 1300 can involve providing the sharing links to a plurality ofclient devices or users in order to share the smart pointer (504) withsuch client devices or users.

If a security threat associated with a shared link is detected, such asunauthorized access to a link, method 1300 can include retroactivelyrevoking the associated access rights from the shared link (and/or anycopies of the shared link) and/or downgrading the shared link to areference link (e.g., 1106) in order to prevent unauthorized access tothe smart pointer (and/or its associated content) and mitigate thesecurity threat. The reference link (e.g., 1106) can be used by anyusers or devices that have rightful access to the shared link or areauthorized to use the shared link, which have since lost any accessconferred by the shared link as a result of the revocation of associatedaccess rights and/or the downgrading of the shared link to a referencelink, to request and regain access to the smart pointer. For example,the user can send an access request including the reference link to thecontent management system (110), which can then provide the user withanother link having the requested access rights or convert the referencelink to a link configured with the requested access rights, such as aview link (e.g., 1102) or an edit link (e.g., 1104).

Turning now to method 1320 shown in FIG. 13B, at step 1322, method 1320can include receiving a request to access a canonical content item(e.g., 520) stored at a content management system (e.g., 110). Thecanonical content item can include a representation of a content item(e.g., a representation, copy or version of third-party cloud servicecontent item 502) stored at a cloud service (e.g., 302, 304, 306, 170).The representation of the content item and the content item in method1320 can be or represent a cloud-backed content item or a cloud-basedcontent item.

The content and features of the content item can be accessed through anonline application (e.g., third-party cloud service application 604)associated with the cloud service. The online application can havenative support for the content item, including the content and featuresof the content item. In some cases, the content and features of thecontent item may only be accessible or supported through the onlineapplication or through a different application using the approachesdescribed herein.

In some cases, the canonical content item stored on the contentmanagement system can include some or all of the content of the contentitem (and the canonical content item). Moreover, in some cases, thecontent and some of the features or functionality of the canonicalcontent item can be accessed or supported by one or more localapplications on one or more client devices (e.g., 150), while additionalfeatures or functionalities may only be accessible through the cloudservice, the online application associated with the cloud service,and/or through the one or more local applications using the approachesdescribed herein

The canonical content item can be stored at a user account (e.g., 704)registered at the content management system (110). The user account caninclude the canonical content item as well as other content items suchas smart pointers, basic pointers, traditional content items, folders,images, videos, documents, audio content items, files, collections,and/or any other type of digital data. In some aspects, the contentitems on the user account can be stored on the content management system(110) as well as one or more client devices (e.g., 150). Moreover, oneor more of the content items (and/or associated changes) on the useraccount can be synchronized between the content management system (110)and the one or more client devices (e.g., 150) in order to maintain aconsistent copy of the content items across the content managementsystem (110) and the one or more client devices (e.g., 150).

In some cases, the canonical content item (520) can be stored along withother content items on a user account at the content management systemand according to a filesystem storage scheme or other organizationscheme for storing the canonical content item and any other contentitems on the user account. For example, the canonical content item canbe stored with other content items in a hierarchical file system orstorage scheme, and visually depicted in storage as a content item suchas a file or document. Thus, the content management system (110) canprovide access control and organization for the canonical content itemas well as any other content items on the user account.

At step 1324, method 1320 can include, in response to the canonicalcontent item (520) being invoked, sending, from a cloud contentintegration element (e.g., 602) on a local application (e.g., clientapplication 152 or browser application 166) to the cloud service (e.g.,302, 304, 306, or 170), a request (e.g., 756, 778, 802) for one or morefeatures of the content item (e.g., 502) associated with the canonicalcontent item (520). In some examples, the request for the one or morefeatures can include a unique ID associated with the canonical contentitem and/or the content item; authentication information; a title of thecontent item and/or the canonical content item; access controlpermissions configured at the content management system (110) for thecanonical content item, the content, and/or the content item; etc. Theaccess control permissions can correspond to a user account (e.g., 704)that is associated with the request for the content and registered atthe content management system (110).

In some aspects, the local application may not provide native supportfor the content item, the content in the content item, and/or featuresor functionalities associated with the content item. Instead, the localapplication may implement the cloud content integration element (e.g.,602) to provide support for the content item and the canonical contentitem, the content in the content item and the canonical content item,and/or features or functionalities associated with the content item andthe canonical content item. The features or functionalities can includeone or more features or functionalities provided by the cloud serviceand accessible through the online application (e.g., 604) associatedwith the cloud service. Non-limiting examples of features orfunctionalities associated with the content item can include commenting,notifications, bi-directional communications or interactions betweenusers working on the content item, live editing or collaborationsessions, tasks, editing, sharing, activity feeds, content or metadataupdates, etc.

At step 1326, method 1320 can include receiving, at the cloud contentintegration element (e.g., 602) on the local application (e.g., 152 or166) and from the cloud service (e.g., 302, 304, 306, or 170), metadatafor enabling the one or more features of the content item (e.g., 502)associated with the canonical content item. In some cases, the cloudcontent integration element (e.g., 602) can also receive other contentor data associated with the content item, such as indexable content, acontent or document preview, and/or any other data or informationassociated with the content item. Moreover, in some examples, themetadata can include one or more comments, one or more tasks, state, oneor more events, one or more updates, user activity information, statusinformation, authoring data, other collaboration information, etc.

At step 1328, method 1320 can include, in response to receiving themetadata for enabling the one or more features of the content item(e.g., 502), providing, on the local application (e.g., 152 or 166), theone or more features of the content item and a content of the contentitem as part of a rendered instance (e.g., 610) of the canonical contentitem (520). The content can be presented within the rendered instance ofthe canonical content item so as to mirror or resemble the content itemon the cloud service when rendered or displayed for a user. In someexamples, the rendered instance of the canonical content item can bepresented along with the content without translating the content priorto presentation of the content.

Moreover, the content can be presented along with the one or morefeatures associated with the content item. The one or more features caninclude one or more collaboration features such as, for example andwithout limitation, live commenting, live editing, bi-directionalcommunications between users working on the content item and thecanonical content item, user activity feeds or notifications, authoringinformation, sharing features, collaboration sessions, content and/ormetadata updates, tasks, etc.

The cloud content integration element (e.g., 602) on the localapplication and/or the content management system (110) can allow data(e.g., content, metadata, events, etc.) added or modified on the contentitem in the cloud service to be implemented on the canonical contentitem (520), and vice versa. For example, if a user renames the contentitem on the cloud service, the cloud service can provide the change tothe content item associated with the canonical content item (520) bysending an update to the cloud content integration element (e.g., 602)and/or the content management system (110). When the cloud contentintegration element (e.g., 602) and/or the content management system(110) receives the update from the cloud service, the cloud contentintegration element (e.g., 602) and/or the content management system(110) can rename the canonical content item (520) accordingly to matchthe renaming of the content item.

The cloud content integration element (e.g., 602) and/or the contentmanagement system (110) can also enable collaborative functionalitiesand live editing or collaboration sessions between users working on thecanonical content item (520) and the content item on the cloud service.For example, the cloud content integration element (e.g., 602) and/orthe content management system (110) can communicate with the cloudservice to exchange information and communications, thereby providingsupport for bi-directional or two-way communications between thecanonical content item (520) and the content item on the cloud service.

To illustrate, comments or messages created from, or added to, thecontent item on the cloud service can be propagated to the canonicalcontent item (e.g., via the cloud content integration element and/or thecontent management system) so a user working on the canonical contentitem (520) can view or interact with the comments or messages createdfrom, or added to, the content item and received from the cloud service,and vice versa. A user working on the canonical content item (520) canreceive or view the comments or messages from the rendered instance ofthe canonical content item and reply to the comments or messages fromthe canonical content item. Any replies added by the user from thecanonical content item can be similarly propagated to the content itemon the cloud service so any users working on the content item canreceive and view such replies. Such collaborations and interactionsbetween users can be exchanged and implemented between the canonicalcontent item and the content item hosted by the cloud service to providean integrated, collaborative experience across all platforms (e.g., thecontent management system, the local application, the cloud service,etc.).

In some aspects, the local application can perform filesystem operations(e.g., 1002) and/or other file or content operations on the canonicalcontent item, such as copy operations, move operations, createoperations, delete operations, purge operations, restore operations,rename operations, version history operations, sharing operations, etc.The local application can propagate any changes resulting from suchoperations to the content item on the cloud service. For example, thelocal application can implement the cloud content integration element(e.g., 602) to send updates (e.g., 762, 790, 1006) to the cloud servicewith the changes from the operations, which the cloud service can use toupdate the content item on the cloud service. The changes can include,for example, changes to the content item, changes to metadata of thecontent item, changes to the content of the content item, changes to thecanonical content item, etc.

In some cases, method 1320 can include receiving, at the cloud contentintegration element (e.g., 602) on the local application and from thecloud service, metadata identifying a comment added to the content item(e.g., 502) stored on the cloud service, and presenting, on the localapplication, the comment with the rendered instance of the canonicalcontent item. The comment can be a comment added by a remote userworking on the content item from the cloud service or a remote userworking on a rendered instance of another copy of the canonical contentitem. Moreover, the comment can be presented within the renderedinstance of the canonical content item, within a separate user interfaceor application, or within a message or notification to the user of thelocal application. Thus, a user viewing or working on the renderedinstance of the canonical content item can receive or view commentsadded to the content item by other users and thereby obtain acollaborative experience when accessing or working on the renderedinstance of the canonical content item.

In some cases, the local application can receive one or more commentsadded to the rendered instance of the canonical content item from thelocal application and propagate the one or more comments to the cloudservice for inclusion or implementation in the content item on the cloudservice. For example, when the local application receives a commentadded by a user working with the rendered instance of the canonicalcontent item at the local application, it can use the cloud contentintegration element (e.g., 602) to send an update message (e.g., 762,790) to the cloud service. The update message can identify the commentadded by the user to the rendered instance of the canonical contentitem. The cloud service can receive the update message and apply or addthe comment from the update message to the content item on the cloudservice. This way, comments added to the content item on the cloudservice and comments added to the rendered instance of the canonicalcontent item can be exchanged between the local application and thecloud service to provide a collaborative experience and maintainconsistency between the content item on the cloud service and thecanonical content item.

In some cases, the cloud content integration element (e.g., 602) on thelocal application can receive, from the cloud service, data associatedwith the content item, such as metadata (e.g., comments, activity,events, tasks, content item information, update information, etc.)associated with the content item, one or more previews (e.g., a contentitem preview such as a text or image preview), indexable content (e.g.,text, image, and/or other digital content that can be indexed forsearching) corresponding to the content item, etc. The data from thecloud service can be presented by the local application as part of therendered instance of the canonical content item, displayed on a separateinterface, presented on a message or notification, depicted in storage(e.g., as a file or document in storage), etc.

Moreover, in some cases, the data or portions of the data can be indexedfor searching. For example, the local application can receive a searchrequest from a user which includes a query for a portion of the dataand, in response to the search request, the local application can searchany indexed data on the user account (e.g., 704) for the portion of thedata associated with the search request. The local application can thenpresent a search result to the user including any matches or, if nomatches are found, an indication that no matches were found.

In some cases, the data associated with the content item can include apreview of the content item (or the canonical content item) and/or anindication of user activity associated with the content item and thecanonical content item. The user activity can include any interactionsbetween a user(s) and the content item, any events generated by auser(s) working on the content item, etc. The preview can include, forexample, a preview (e.g., an image preview, a text preview, a filepreview, etc.) of the content item and/or the canonical content item, apreview of one or more portions of content in the content item and/orthe canonical content item, etc.

The local application can present the preview and/or the user activityto a user having access to the canonical content item or viewing/workingon the rendered instance of the canonical content item. For example, thelocal application can display an activity feed or activity notificationidentifying the user activity. In some examples, the preview can bestored in the user account (e.g., 704) and depicted as a content item instorage. The user can view the preview from storage without accessingthe content item or obtaining a rendered instance of the canonicalcontent item. Moreover, the preview can be used by the user's device(e.g., 150) or the content management system (110) to search for contentassociated with the content item and/or the canonical content item.

In some cases, method 1320 can include receiving a request to open acopy of a specific canonical content item (e.g., a copy of a canonicalcontent item representing a specific cloud-backed or cloud-based contentitem) using a specific application that is different from an onlineapplication or editor that is associated with the specific canonicalcontent item and provides native support for the specific canonicalcontent item and its associated content and features/functionalities.Method 1320 can further include identifying a live collaboration sessionbetween users interacting with the specific canonical content itemand/or an associated third-party content item (e.g., 502) anddetermining that the specific application does not support livecollaboration for the copy of the specific canonical content item.Method 1320 can also include providing a prompt to the requesting useror device with an option to join the live collaboration session via adifferent application that supports live collaboration for the specificcontent item, and in response to receiving an acceptance of the optionto join the live collaboration session, routing the requesting user ordevice to the different application and/or joining the requesting useror device to the live collaboration session via the differentapplication.

In some cases, method 1320 can also include generating a plurality ofsharing links to the canonical content item (520). The sharing links canbe configured with various access rights, and the sharing links can beused to share the canonical content item with users and provide suchusers a specific level of access to the canonical content item. Forexample, the plurality of sharing links can include a view link (e.g.,1102) configured with read-only access rights to the canonical contentitem (520), an edit link (e.g., 1104) configured with edit access rightsto the canonical content item (520), and/or a reference link (e.g.,1106) that uniquely identifies the canonical content item (520) andconfers no access rights to the canonical content item (520). The method1320 can involve providing the sharing links to a plurality of clientdevices or users in order to share the canonical content item (520) withsuch client devices or users.

If a security threat associated with a shared link is detected, such asunauthorized access to a link, method 1320 can include retroactivelyrevoking the associated access rights from the shared link (and/or anycopies of the shared link) and/or downgrading the shared link to areference link (e.g., 1106) in order to prevent unauthorized access tothe canonical content item (and/or its associated content) and mitigatethe security threat. The reference link (e.g., 1106) can be used by anyusers or devices that have rightful access to the shared link or areauthorized to use the shared link, which have since lost any accessconferred by the shared link as a result of the revocation of associatedaccess rights and/or the downgrading of the shared link to a referencelink, to request and regain access to the canonical content item. Forexample, the user can send an access request including the referencelink to the content management system (110), which can then provide theuser with another link having the requested access rights or convert thereference link to a link configured with the requested access rights,such as a view link (e.g., 1102) or an edit link (e.g., 1104).

With reference to method 1340 shown in FIG. 13C, at step 1342, method1340 can include storing content items at one or more user accounts(e.g., 704) on a content management system (110). In some cases, thecontent items can be stored along with other content items on the one ormore user accounts at the content management system and according to afilesystem storage scheme or other organization scheme for storing thecontent items and any other content items on the one or more useraccounts. For example, the content items can be stored with othercontent items in a hierarchical file system or storage scheme, andvisually depicted in storage. Thus, the content management system (110)can provide access control and organization for the content items aswell as any other content items on the one or more user accounts.

The content items can include one or more traditional content items, oneor more representations of one or more cloud-based content items, one ormore representations of one or more cloud-backed content items, one ormore smart pointers, one or more canonical content items, one or morebasic pointers, etc. In example method 1340, the content items include atraditional content item, a representation of a cloud-based contentitem, and a representation of a cloud-backed content item. Therepresentation of the cloud-based content item and the representation ofthe cloud-backed content item can include a smart pointer (e.g., 504)and/or a canonical content item (e.g., 520).

The traditional content item can be supported by one or more localapplications without use or involvement of a cloud service (e.g., 302,304, 306, 170). The content and features of the cloud-based content itemcan be enabled by the cloud service and designed for access through anonline application associated with the cloud service. The cloud-backedcontent item can have some content and features supported by one or morelocal applications without use or involvement of the cloud service orthe online application associated with the cloud service, as well asadditional features designed for access through the cloud service andthe online application associated with the cloud service.

At step 1344, method 1340 can include, in response to the traditionalcontent item being invoked (e.g., by a client device or application),presenting the content and features of the traditional content item viaone of the one or more local applications (e.g., 152, 166) that supportthe content and features of the traditional content item.

At step 1346, method 1340 can include, in response to a request toaccess the representation of the cloud-based content item and therepresentation of the cloud-backed content item, sending, to the cloudservice, from one or more cloud content integration elements (e.g., 602)on at least one local application (e.g., 152, 166) from the one or morelocal applications, a request for the additional features associatedwith the cloud-backed content item and the content and/or featuresassociated with the cloud-based content item. In some cases, the requestfor the additional features associated with the cloud-backed contentitem and the content and/or features associated with the cloud-basedcontent item can include authentication information associated with thecontent management system, unique identifiers associated with thecloud-backed content item and the cloud-based content item, accesspermissions configured at the content management system for thecloud-backed content item and the cloud-based content item, and/or anyother information.

In some cases, the request can also request some or all of the contentassociated with the cloud-backed content item. Moreover, the requestedfeatures associated with the cloud-based content item and thecloud-backed content item can include collaboration and other featuressuch as, for example and without limitation, live commenting, liveediting, live communications between users working on such contentitems, authoring, tasks, state information, activity feeds ornotifications, previewing features, indexing features, content and/ormetadata updates, collaboration sessions, sharing features, etc.

At step 1348, method 1340 can include receiving, from the cloud service,metadata for enabling the additional features associated with thecloud-backed content item and the features associated with thecloud-based content item. In some cases, method 1340 can also includereceiving some or all of the content associated with the cloud-backedand/or cloud-based content item. The metadata can include, for example,one or more comments, one or more tasks, one or more edits, one or morecontent operations, one or more previews, one or more notifications, oneor more events, user activity information, sharing information, indexingdata, state data, one or more messages or communications, one or morecontent or metadata updates or changes, content item information, etc.

Based on the metadata, at step 1350, method 1340 can include providing,via the one or more cloud content integration elements and the at leastone local application, the additional features and respective contentassociated with the cloud-backed content item and the content andfeatures associated with the cloud-based content item as part ofrendered instances of the cloud-backed content item and the cloud-basedcontent item.

In some cases, method 1340 can include presenting, at the one or moreuser accounts on the content management system, the content itemsincluding the traditional content item, the representation of thecloud-based content item, and the representation of the cloud-backedcontent item. The content items can be presented according to anorganization associated with the one or more user accounts and/or anaccess control associated with the one or more user accounts.

In some examples, a cloud content integration element (e.g., 602) on alocal application and/or the content management system (110) can allowdata (e.g., content, metadata, events, etc.) added or modified on a copyof the cloud-based and/or cloud-backed content item in the cloud serviceto be implemented on the cloud-based and/or cloud-backed content item onthe content management system, and vice versa. For example, if a userrenames a cloud-based or cloud-backed content item on the cloud service,the cloud service can provide the change to the content item by sendingan update to the cloud content integration element (e.g., 602) and/orthe content management system (110). When the cloud content integrationelement (e.g., 602) and/or the content management system (110) receivesthe update from the cloud service, the cloud content integration element(e.g., 602) and/or the content management system (110) can rename thecloud-based or cloud-backed content item accordingly to match therenaming of the content item.

The cloud content integration element (e.g., 602) and/or the contentmanagement system (110) can also enable collaborative functionalitiesand live editing or collaboration sessions between users working on thecloud-based and/or cloud-backed content items on the cloud service andthe content management system. For example, the cloud contentintegration element (e.g., 602) and/or the content management system(110) can communicate with the cloud service to exchange information andcommunications, thereby providing support for bi-directional or two-waycommunications between the cloud-based and/or cloud-backed content itemson the cloud service and the content management system.

To illustrate, comments or messages created from, or added to, thecloud-based and/or cloud-backed content items on the cloud service canbe propagated to the cloud-based and/or cloud-backed content items onthe content management system (e.g., via the cloud content integrationelement and/or the content management system) so a user working on thecloud-based and/or cloud-backed content items on the content managementsystem can view or interact with the comments or messages created from,or added to, the cloud-based and/or cloud-backed content items andreceived from the cloud service, and vice versa. A user working on thecloud-based and/or cloud-backed content items can receive or view thecomments or messages from the rendered instance of the cloud-basedand/or cloud-backed content items and reply to the comments or messagesfrom the cloud-based and/or cloud-backed content items on the cloudservice or the content management system. Any replies added by the userfrom the cloud-based and/or cloud-backed content items on the contentmanagement system can be similarly propagated to the cloud-based and/orcloud-backed content items on the cloud service so any users working onthe content item can receive and view such replies. Such collaborationsand interactions between users can be exchanged and implemented betweenthe cloud-based and/or cloud-backed content items on the contentmanagement system and the cloud service to provide an integrated,collaborative experience across all platforms (e.g., the contentmanagement system, the local application, the cloud service, etc.).

In some aspects, a local application can perform filesystem operations(e.g., 1002) and/or other file or content operations on the cloud-basedand/or cloud-backed content items, such as copy operations, moveoperations, create operations, delete operations, purge operations,restore operations, rename operations, version history operations,sharing operations, etc. The local application can propagate any changesresulting from such operations to the cloud-based and/or cloud-backedcontent items on the cloud service. For example, the local applicationcan implement the cloud content integration element (e.g., 602) to sendupdates (e.g., 762, 790, 1006) to the cloud service with the changesfrom the operations, which the cloud service can use to update thecloud-based and/or cloud-backed content items on the cloud service. Thechanges can include, for example, changes to the cloud-based and/orcloud-backed content items, changes to metadata of the cloud-basedand/or cloud-backed content items, changes to the content of thecloud-based and/or cloud-backed content items, changes to thecloud-based and/or cloud-backed content items, etc.

In some cases, method 1340 can include receiving, at a cloud contentintegration element (e.g., 602) on a local application and from thecloud service, metadata identifying a comment added to the cloud-basedand/or cloud-backed content items stored on the cloud service, andpresenting, on the local application, the comment with a renderedinstance of the cloud-based and/or cloud-backed content items. Thecomment can be a comment added by a remote user working on thecloud-based and/or cloud-backed content items from the cloud service ora remote user working on a rendered instance of another copy of thecloud-based and/or cloud-backed content items. Moreover, the comment canbe presented within the rendered instance of the cloud-based and/orcloud-backed content items, within a separate user interface orapplication, or within a message or notification to the user of thelocal application. Thus, a user viewing or working on the renderedinstance of the cloud-based and/or cloud-backed content items canreceive or view comments added to the cloud-based and/or cloud-backedcontent items by other users and thereby obtain a collaborativeexperience when accessing or working on the rendered instance of thecloud-based and/or cloud-backed content items.

In some cases, the local application can receive one or more commentsadded to the rendered instance of the cloud-based and/or cloud-backedcontent items from the local application and propagate the one or morecomments to the cloud service for inclusion or implementation in thecloud-based and/or cloud-backed content items on the cloud service. Forexample, when the local application receives a comment added by a userworking with the rendered instance of the cloud-based and/orcloud-backed content items at the local application, it can use thecloud content integration element (e.g., 602) to send an update message(e.g., 716, 738, 762, 790) to the cloud service. The update message canidentify the comment added by the user to the rendered instance of thecloud-based and/or cloud-backed content items. The cloud service canreceive the update message and apply or add the comment from the updatemessage to the cloud-based and/or cloud-backed content items on thecloud service. This way, comments added to the cloud-based and/orcloud-backed content items on the cloud service and comments added tothe rendered instance of the cloud-based and/or cloud-backed contentitems can be exchanged between the local application and the cloudservice to provide a collaborative experience and maintain consistencybetween the cloud-based and/or cloud-backed content items on the cloudservice and the content management system.

In some cases, the cloud content integration element (e.g., 602) on thelocal application can receive, from the cloud service, data associatedwith the cloud-based and/or cloud-backed content items, such as metadata(e.g., comments, activity, events, tasks, content item information,update information, etc.) associated with the cloud-based and/orcloud-backed content items, one or more previews (e.g., a content itempreview such as a text or image preview), indexable content (e.g., text,image, and/or other digital content that can be indexed for searching)corresponding to the cloud-based and/or cloud-backed content items, etc.The data from the cloud service can be presented by the localapplication as part of the rendered instance of the cloud-based and/orcloud-backed content items, displayed on a separate interface, presentedon a message or notification, depicted in storage (e.g., as a file ordocument in storage), etc.

Moreover, in some cases, the data or portions of the data can be indexedfor searching. For example, the local application can receive a searchrequest from a user that includes a query for a portion of the data and,in response to the search request, the local application can search anyindexed data on the user account (e.g., 704) for the portion of the dataassociated with the search request. The local application can thenpresent a search result to the user including any matches or, if nomatches are found, an indication that no matches were found.

In some cases, the data associated with the cloud-based and/orcloud-backed content items can include a preview of the cloud-basedand/or cloud-backed content items and/or an indication of user activityassociated with the cloud-based and/or cloud-backed content items. Theuser activity can include any interactions between a user(s) and thecloud-based and/or cloud-backed content items, any events generated by auser(s) working on the cloud-based and/or cloud-backed content items,etc. The preview can include, for example, a preview (e.g., an imagepreview, a text preview, a file preview, etc.) of the cloud-based and/orcloud-backed content items, a preview of one or more portions of contentin the cloud-based and/or cloud-backed content items, etc.

The local application can present the preview and/or the user activityto a user having access to the cloud-based and/or cloud-backed contentitems or viewing/working on a rendered instance of the cloud-basedand/or cloud-backed content items. For example, the local applicationcan display an activity feed or activity notification identifying theuser activity. In some examples, the preview can be stored in the useraccount (e.g., 704) and depicted as a content item in storage. The usercan view the preview from storage without accessing the cloud-basedand/or cloud-backed content items or obtaining a rendered instance ofthe cloud-based and/or cloud-backed content items. Moreover, the previewcan be used by the user's device (e.g., 150) or the content managementsystem (110) to search for content associated with the cloud-basedand/or cloud-backed content items.

In some cases, method 1340 can include receiving a request to open acopy of a specific cloud-based and/or cloud-backed content item using aspecific application that is different from an online application oreditor that is associated with the specific cloud-based and/orcloud-backed content item and provides native support for the specificcloud-based and/or cloud-backed content item and its associated contentand features/functionalities. Method 1340 can further includeidentifying a live collaboration session between users interacting withthe specific cloud-based and/or cloud-backed content item anddetermining that the specific application does not support livecollaboration for the copy of the specific cloud-based and/orcloud-backed content item. Method 1340 can also include providing aprompt to the requesting user or device with an option to join the livecollaboration session via a different application that supports livecollaboration for the specific cloud-based and/or cloud-backed contentitem, and in response to receiving an acceptance of the option to jointhe live collaboration session, routing the requesting user or device tothe different application and/or joining the requesting user or deviceto the live collaboration session via the different application.

In some cases, method 1340 can also include generating a plurality ofsharing links to the cloud-based and/or cloud-backed content item. Thesharing links can be configured with various access rights, and thesharing links can be used to share the cloud-based and/or cloud-backedcontent item with users and provide such users a specific level ofaccess to the cloud-based and/or cloud-backed content item. For example,the plurality of sharing links can include a view link (e.g., 1102)configured with read-only access rights to the cloud-based and/orcloud-backed content item, an edit link (e.g., 1104) configured withedit access rights to the cloud-based and/or cloud-backed content item,and/or a reference link (e.g., 1106) that uniquely identifies thecloud-based and/or cloud-backed content item and confers no accessrights to the cloud-based and/or cloud-backed content item. The method1340 can involve providing the sharing links to a plurality of clientdevices or users in order to share the cloud-based and/or cloud-backedcontent item with such client devices or users.

If a security threat associated with a shared link is detected, such asunauthorized access to a link, method 1340 can include retroactivelyrevoking the associated access rights from the shared link (and/or anycopies of the shared link) and/or downgrading the shared link to areference link (e.g., 1106) in order to prevent unauthorized access tothe cloud-based and/or cloud-backed content item and mitigate thesecurity threat. The reference link (e.g., 1106) can be used by anyusers or devices that have rightful access to the shared link or areauthorized to use the shared link, which have since lost any accessconferred by the shared link as a result of the revocation of associatedaccess rights and/or the downgrading of the shared link to a referencelink, to request and regain access to the cloud-based and/orcloud-backed content item. For example, the user can send an accessrequest including the reference link to the content management system(110), which can then provide the user with another link having therequested access rights or convert the reference link to a linkconfigured with the requested access rights, such as a view link (e.g.,1102) or an edit link (e.g., 1104).

With reference to method 1360 shown in FIG. 13D, at step 1362, method1360 can include storing a content item in a shared folder stored on acontent management system (110), the content item representing acloud-backed content item associated with a cloud content provider(e.g., 302, 304, 306, 170) or a cloud-based content item associated withthe cloud content provider (e.g., 302, 304, 306, 170). In some cases,the content of the content item can be stored on the content managementsystem. For example, the content item can be a canonical content itemrepresenting a cloud-based or cloud-backed content item stored on thecontent management system. In other cases, the content of the contentitem can be stored on the cloud content provider. For example, thecontent item can be a smart pointer stored on the content managementsystem and referencing a cloud-based or cloud-backed content item storedon the cloud content provider.

At step 1364, method 1360 can include receiving, from a user account(704) on the content management system, a request to access the contentitem in the shared folder. For example, the content management systemcan receive a request from the user account to access the content itemfrom the shared folder using a local application (e.g., 152, 166) on aclient device (150) associated with a user. In some cases, the requestcan be generated when a user associated with the user account invokesthe content item from the shared folder, selects the content item,attempts to access the content item from the shared folder, etc.

At step 1366, method 1360 can include determining, based on accesspermissions configured at the content management system, whether theuser account has an access permission allowing the user account toaccess the shared folder and/or the content item. For example, thecontent management system can check access permissions set for theshared folder and/or the content item to determine if the user accounthas an access permission set for allowing the user account to access theshared folder and/or the content item.

In some cases, the access permission can include a content itempermission inherited by the content item from a shared folder permissionset at the content management system for the shared folder. For example,the content item can inherit permissions from the shared folder itresides in. Thus, if the user account has an access permission allowingthe user account access to the shared folder, the user account caninherit from the shared folder an access permission allowing access tothe content item in the shared folder.

In some examples, the shared folder permission can include a readpermission providing the user account read access to the shared folderor an edit permission providing the user account edit access to theshared folder. The read permission can include, for example, a viewand/or read-only permission. The edit permission can include, forexample, a permission granting modification rights, write access rights,full control rights (e.g., add, modify, move, delete, rename, etc.),execute privileges allowing the user account to run executable contentitems, etc.

Moreover, in some examples, the content item permission can include acontent item read permission inherited from the read permissionassociated with the shared folder or a content item edit permissioninherited from the edit permission associated with the shared folder.The content management system can grant the user account access to thecontent item based on the content item permission inherited by thecontent item from the shared folder permission.

If the content management system determines that the user account doesnot have an access permission configured allowing the user account toaccess the shared folder or the content item, the content managementsystem can prevent the user account from accessing the content item. Theuser associated with the user account can, in turn, optionally requestaccess to the content item from a user having sufficient access to theshared folder and/or the content item to share the content item and/orthe shared folder with the user account.

On the other hand, if the content management system determines that theuser account has an access permission configured allowing the useraccount to access the shared folder or the content item, at step 1368,method 1360 can include granting the user account access to the contentitem based on a determination that the user account has the accesspermission.

At step 1370, method 1360 can include providing, to the user account, acontent of the content item and one or more features of the contentitem, the one or more features being supported by the cloud contentprovider and provisioned at least partly through the cloud contentprovider. In some cases, the one or more features can be designed foraccess via a native online application (e.g., third-party cloud serviceapplication 604) associated with the cloud content provider.

In some examples, providing the one or more features of the content itemcan include sending, from a cloud content integration element (702) on alocal application (e.g., 152, 166) to the cloud content provider, arequest for the one or more features of the content item; receiving, atthe cloud content integration element on the local application, from thecloud content provider, metadata for enabling the one or more featuresof the content item; and in response to receiving the metadata forenabling the one or more features of the content item, providing, on thelocal application, the content item and the one or more features of thecontent item as part of a rendered instance of the canonical contentitem. In this example, the one or more features can be provided based onthe metadata.

The local application can be a different application than the nativeonline application (e.g., third-party cloud service application 604)associated with the cloud content provider. In some cases, the localapplication may not natively support the content and/or the one or morefeatures associated with the content item. Moreover, the localapplication can provide the one or more features and the content of thecontent item as part of the rendered instance of the canonical contentitem without translating the content prior to rendering the content. Thelocal application can thus provide support for the content and featuresof the content item without translating the content prior to renderingthe content and despite lacking native support for the content and/orthe features of the content item. Such support can be provided aspreviously described herein.

In some cases, the content of the content item can be stored on andprovided from the cloud content provider. For example, the content itemcan be a smart pointer (504) representing the cloud-backed content itemor the cloud-backed content item. The smart pointer can reference thecloud-backed or cloud-based content item, which can have its contentstored on the cloud content provider. To provide the content and the oneor more features of the content item (e.g., the content and one or morefeatures associated with the smart pointer), the local application cansend, from a cloud content integration element (702) to the cloudcontent provider, a request for the content and one or more features ofthe content item. The local application can then receive, at the cloudcontent integration element and from the cloud content provider, thecontent of the content item and metadata for enabling the one or morefeatures of the content item. In response to receiving the content ofthe content item and the metadata, the local application can provide thecontent and one or more features of the content item as part of arendered instance of the smart pointer.

The local application can use the metadata to provide the one or morefeatures of the content item. Moreover, the local application canprovide the one or more features and the content of the content item aspart of the rendered instance of the smart pointer without translatingthe content prior to rendering the content. The local application canprovide the content and the one or more features even if the localapplication does not natively support such content and features asdescribed herein.

In some examples, the content item can be a canonical content item (520)stored on the content management system. The content of the content itemcan be stored on the content management system and provided via thecanonical content item. The canonical content item can represent thecloud-backed content item or the cloud-backed content item. Moreover, insome cases, the one or more features can be designed for access via anative online application (e.g., third-party cloud service application604) associated with the cloud content provider.

To provide the content of the canonical content item (e.g., the contentof the content item), the local application can retrieve the contentfrom storage at the content management system or a client device (150)storing content items of a user account registered at the contentmanagement system. Moreover, to provide the one or more features of thecanonical content item (e.g., the one or more features of the contentitem), the local application can send, from a cloud content integrationelement (e.g., 702) to the cloud content provider, a request for the oneor more features of the content item. The local application can receive(e.g., via the cloud content integration element) from the cloud contentprovider, metadata for enabling the one or more features of the contentitem. In response to receiving the metadata for enabling the one or morefeatures of the content item, the local application can provide thecontent of the content item (e.g., retrieved from storage) and the oneor more features of the content item as part of a rendered instance ofthe canonical content item.

The one or more features can be provided based on the metadata. Thelocal application can provide the one or more features and the contentof the content item as part of the rendered instance of the canonicalcontent item without translating the content prior to rendering thecontent. Moreover, the local application can provide the content and theone or more features as described herein, even if it lacks nativesupport for the content and/or features.

In some cases, the one or more features can include one or morecollaboration functionalities. The one or more collaborationfunctionalities can include, for example and without limitation, activecommenting on the content of the content item, bi-directionalcommunication between user accounts working on the content item,accessing user activity associated with user accounts working on thecontent item, authoring functionalities, previewing functionalities,sharing functionalities, etc.

In some implementations, method 1360 can include receiving, from thecontent management system, one or more additional features supported bythe content management system. The one or more additional features canprovide additional functionality for the content item. In some examples,the one or more additional features can include organization settingsassociated with the one or more user accounts registered at the contentmanagement system, sharing features, access control, etc.

In some cases, the content management system can provide the source oftruth for permissions of cloud-based and/or cloud-backed content items,such as canonical content items, stored at the content management systemas well as one or more cloud content providers. For example, while thecontent item can have synchronized copies on the cloud content providerand/or can have its content stored at the cloud content provider (e.g.,if the content item is a smart pointer), the content management systemcan nevertheless provide the source of truth for permissions to thecontent item.

Thus, access to the content item, including reading, editing, renaming,moving, sharing, deleting, etc., can be controlled by the contentmanagement system. In some cases, the content management system canprovide a user on the content management system certain access to thecontent item even if the cloud content provider does not provide or hasnot enabled such access to the user. For example, assume User A and UserB have a cloud-based or cloud-backed content item stored at the cloudcontent provider. Assume that User A then stores a copy of thecloud-based or cloud-backed content item, such as a canonical contentitem, in a folder on the content management system and shared the folderwith User C at the content management system. Despite User C not havingpermission at the cloud content provider to access the cloud-based orcloud-backed content item and its contents, User C in this example maybe able to access the cloud-based or cloud-backed content item from theshared folder on the content management system.

Thus, the content management system can implement the access permissionson the content management system (e.g., the access permissions for theshared folder, the cloud-based or cloud-backed content item, and/or UserC) to determine whether to provide User C access to the cloud-based orcloud-backed content item. If User C then shares the cloud-based orcloud-backed content item with User D at the content management system(e.g., by moving or copying the cloud-based or cloud-backed content itemto a folder shared between User C and User D), User D can obtain accessto the cloud-based or cloud-backed content item based on the accesspermissions at the content management system even if User D does nothave sufficient access to the cloud-based or cloud-backed content itemthrough the cloud content provider.

However, in some implementations, the content management system canimplement policies preventing users from sharing some or all types ofcloud-based or cloud-backed content items (e.g., canonical contentitems, smart pointers, etc.) outside of the content management system'secosystem and/or with users that do not have accounts at the contentmanagement system. For example, in some cases, the content managementsystem may implement a policy that would prevent a user from sharing asmart pointer on the content management system, which would have itsassociated content stored at the cloud content provider, with users thatdo not have accounts at the content management system and/or storing thesmart pointer outside of the content management system's ecosystem.

In some cases, a user can access the content item stored on the sharedfolder at the content management system from the native onlineapplication associated with the content item and the cloud contentprovider. The access permissions (e.g., access control lists) at thecontent management system can still control the level of access (if any)provided to the user. However, in some cases, the native onlineapplication can also apply access permissions defined at the cloudcontent provider for the content item (or an associated cloud-based orcloud-backed content item at the cloud content provider).

For example, the native online application can apply access permissionsset at the cloud content provider in addition to, or on top of, theaccess permissions at the content management system. In someimplementations, if there is a conflict between the access permissionsat the content management system and the access permissions at the cloudcontent provider, the access permissions at the content managementsystem control. In other implementations, the more restrictive accesspermissions—between the access permissions at the content managementsystem and the cloud content provider—can control. In yet otherimplementations, the more permissive access permissions—between theaccess permissions at the content management system and the cloudcontent provider

-   -   can control.

A non-limiting, illustrative example snippet of code for access to acloud-based or cloud-backed content item on the content managementsystem (CMS) is provided below:

 1 get(″/ContentItem/{ContentItem_ID}”, function(request, response) {  2// Request access via an API associated with CMS 110 (e.g., 310, 312,314)  3 access =httpPost(″https://api.CMS.com/Cloud_ContentItems/metadata″, {  4“ContentItem_ID”: request.params.ContentItem_ID  5 });  6  if(access.error) { // user has no permission to access this cloud-based orcloud- backed content item  7  response.write(403);  8 } else {  9 ContentItem_ID = sql.execute( 10 ″SELECT my_ID FROMcms_cloud_content_items WHERE cloud_content_item_id = $1″, 11[request.parains.ContentItem_ID] 12  ); 13 // Show view-only version ofthis content item if no edit access is available 14 Returnrender_ContentItem(ContentItem_ID, content = content, edit =response.is_editor) 15  } 16  })

FIG. 14 shows an example of computing system 1400, which can be forexample any computing device making up client device 150, contentmanagement system 110 or any component thereof in which the componentsof the system are in communication with each other using connection1405. Connection 1405 can be a physical connection via a bus, or adirect connection into processor 1410, such as in a chipsetarchitecture. Connection 1405 can also be a virtual connection,networked connection, or logical connection.

In some embodiments, computing system 1400 is a distributed system inwhich the functions described in this disclosure can be distributedwithin a datacenter, multiple datacenters, a peer network, etc. In someembodiments, one or more of the described system components representsmany such components each performing some or all of the function forwhich the component is described. In some embodiments, the componentscan be physical or virtual devices.

Example computing system 1400 includes at least one processing unit (CPUor processor) 1410 and connection 1405 that couples various systemcomponents including system memory 1415, such as read only memory (ROM)1420 and random access memory (RAM) 1425 to processor 1410. Computingsystem 1400 can include a cache of high-speed memory 1412 connecteddirectly with, in close proximity to, or integrated as part of processor1410.

Processor 1410 can include any general purpose processor and a hardwareservice or software service, such as services 1432, 1434, and 1436stored in storage device 1430, configured to control processor 1410 aswell as a special-purpose processor where software instructions areincorporated into the actual processor design. Processor 1410 mayessentially be a completely self-contained computing system, containingmultiple cores or processors, a bus, memory controller, cache, etc. Amulti-core processor may be symmetric or asymmetric.

To enable user interaction, computing system 1400 includes an inputdevice 1445, which can represent any number of input mechanisms, such asa microphone for speech, a touch-sensitive screen for gesture orgraphical input, keyboard, mouse, motion input, speech, etc. Computingsystem 1400 can also include output device 1435, which can be one ormore of a number of output mechanisms known to those of skill in theart. In some instances, multimodal systems can enable a user to providemultiple types of input/output to communicate with computing system1400. Computing system 1400 can include communications interface 1440,which can generally govern and manage the user input and system output.There is no restriction on operating on any particular hardwarearrangement and therefore the basic features here may easily besubstituted for improved hardware or firmware arrangements as they aredeveloped.

Storage device 1430 can be a non-volatile memory device and can be ahard disk or other types of computer readable media which can store datathat are accessible by a computer, such as magnetic cassettes, flashmemory cards, solid state memory devices, digital versatile disks,cartridges, random access memories (RAMs), read only memory (ROM),and/or some combination of these devices.

The storage device 1430 can include software services, servers,services, etc., that when the code that defines such software isexecuted by the processor 1410, it causes the system to perform afunction. In some embodiments, a hardware service that performs aparticular function can include the software component stored in acomputer-readable medium in connection with the necessary hardwarecomponents, such as processor 1410, connection 1405, output device 1435,etc., to carry out the function.

For clarity of explanation, in some instances the present technology maybe presented as including individual functional blocks includingfunctional blocks comprising devices, device components, steps orroutines in a method embodied in software, or combinations of hardwareand software.

Any of the steps, operations, functions, or processes described hereinmay be performed or implemented by a combination of hardware andsoftware services or services, alone or in combination with otherdevices. In some embodiments, a service can be software that resides inmemory of a client device and/or one or more servers of a contentmanagement system and perform one or more functions when a processorexecutes the software associated with the service. In some embodiments,a service is a program, or a collection of programs that carry out aspecific function. In some embodiments, a service can be considered aserver. The memory can be a non-transitory computer-readable medium.

In some embodiments the computer-readable storage devices, mediums, andmemories can include a cable or wireless signal containing a bit streamand the like. However, when mentioned, non-transitory computer-readablestorage media expressly exclude media such as energy, carrier signals,electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implementedusing computer-executable instructions that are stored or otherwiseavailable from computer readable media. Such instructions can comprise,for example, instructions and data which cause or otherwise configure ageneral purpose computer, special purpose computer, or special purposeprocessing device to perform a certain function or group of functions.Portions of computer resources used can be accessible over a network.The computer executable instructions may be, for example, binaries,intermediate format instructions such as assembly language, firmware, orsource code. Examples of computer-readable media that may be used tostore instructions, information used, and/or information created duringmethods according to described examples include magnetic or opticaldisks, solid state memory devices, flash memory, USB devices providedwith non-volatile memory, networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprisehardware, firmware and/or software, and can take any of a variety ofform factors. Typical examples of such form factors include servers,laptops, smart phones, small form factor personal computers, personaldigital assistants, and so on. Functionality described herein also canbe embodied in peripherals or add-in cards. Such functionality can alsobe implemented on a circuit board among different chips or differentprocesses executing in a single device, by way of further example.

The instructions, media for conveying such instructions, computingresources for executing them, and other structures for supporting suchcomputing resources are means for providing the functions described inthese disclosures.

Although a variety of examples and other information was used to explainaspects within the scope of the appended claims, no limitation of theclaims should be implied based on particular features or arrangements insuch examples, as one of ordinary skill would be able to use theseexamples to derive a wide variety of implementations. Further andalthough some subject matter may have been described in languagespecific to examples of structural features and/or method steps, it isto be understood that the subject matter defined in the appended claimsis not necessarily limited to these described features or acts. Forexample, such functionality can be distributed differently or performedin components other than those identified herein. Rather, the describedfeatures and steps are disclosed as examples of components of systemsand methods within the scope of the appended claims.

Claim language reciting “at least one of” refers to at least one of aset and indicates that one member of the set or multiple members of theset satisfy the claim. For example, claim language reciting “at leastone of A and B” means A, B, or A and B. In other words, claim languagereciting “at least one of A and B” means A and/or B.

What is claimed is:
 1. A method comprising: receiving a request to opena content item using a client application at a first client device;detecting that the content item is open at a second client device from adifferent client application that supports live collaboration; anddirecting the first client device to an instance of the different clientapplication at the first client device.
 2. The method of claim 1,wherein directing the first client device to the instance of thedifferent client application comprises routing a user account associatedwith the first client device to the instance of the different clientapplication.
 3. The method of claim 2, wherein routing the user accountto the instance of the different client application further comprisesopening the content item from the instance of the different clientapplication and establishing a live collaboration session with a seconduser account associated with the second client device.
 4. The method ofclaim 1, wherein the content item comprises at least one of acloud-backed content item or a cloud-based content item.
 5. The methodof claim 4, wherein the cloud-based content item comprises a first typeof content item having content and features enabled by a cloud serviceand designed for access through a native application associated with thecloud service, and wherein the cloud-backed content item comprises asecond type of content item having content and features supported by oneor more local applications without use of the cloud service or thenative application, the cloud-backed content item having additionalfeatures designed for access through the cloud service and the nativeapplication associated with the cloud service.
 6. The method of claim 1,wherein directing the first client device to the instance of thedifferent client application comprises routing a first user accountassociated with the first client device to the instance of the differentclient application and joining the first user account to a livecollaboration session with a second user account associated with thesecond client device.
 7. The method of claim 6, wherein joining thefirst user account to the live collaboration session comprises:determining that a cloud service supports live collaboration for thecontent item; sending, from the instance of the different clientapplication to the cloud service, a request for metadata associated withthe live collaboration session; receiving, at the instance of thedifferent client application and from the cloud service, the metadataassociated with the live collaboration session; based on the metadata,providing, via the instance of the different client application, livecollaboration for the content item.
 8. The method of claim 7, whereinthe metadata comprises collaboration data generated during the livecollaboration session, and wherein providing live collaboration for thecontent item comprises presenting collaboration data in association withthe content item, the collaboration data identifying one or more livecollaboration communications or events.
 9. The method of claim 8,wherein the one or more live collaboration communications or eventscomprise at least one of one or more comments, one or morebi-directional communications between users working on the content item,or user activity associated with users working on the content item. 10.The method of claim 1, further comprising: receiving, from a contentmanagement system, one or more features supported by the contentmanagement system for the content item, the one or more featuresproviding additional functionality to the content item, the one or morefeatures comprising at least one of access control, organizationsettings associated with a user account registered at the contentmanagement system, or sharing features.
 11. A system comprising: one ormore processors; and at least one non-transitory computer-readablemedium having stored therein instructions which, when executed by theone or more processors, cause the system to: receive a request to open acontent item using a client application at a first client device; detectthat the content item is open at a second client device from a differentclient application that supports live collaboration; and direct thefirst client device to an instance of the different client applicationat the first client device.
 12. The system of claim 11, whereindirecting the first client device to the instance of the differentclient application comprises routing a user account associated with thefirst client device to the instance of the different client application.13. The system of claim 12, wherein routing the user account to theinstance of the different client application further comprises openingthe content item from the instance of the different client applicationand establishing a live collaboration session with a second user accountassociated with the second client device.
 14. The system of claim 11,wherein the content item comprises at least one of a cloud-backedcontent item or a cloud-based content item, wherein the cloud-basedcontent item comprises a first type of content item having content andfeatures enabled by a cloud service and designed for access through anative application associated with the cloud service, and wherein thecloud-backed content item comprises a second type of content item havingfeatures supported by one or more applications without use of the cloudservice or the native application, the cloud-backed content item havingadditional features designed for access through the cloud service andthe native application associated with the cloud service.
 15. The systemof claim 11, wherein directing the first client device to the instanceof the different client application comprises routing a first useraccount associated with the first client device to the instance of thedifferent client application and joining the first user account to alive collaboration session with a second user account associated withthe second client device.
 16. The system of claim 15, wherein joiningthe first user account to the live collaboration session comprises:determining that a cloud service supports live collaboration for thecontent item; sending, from the instance of the different clientapplication to the cloud service, a request for metadata associated withthe live collaboration session; receiving, at the instance of thedifferent client application and from the cloud service, the metadataassociated with the live collaboration session; based on the metadata,providing, via the instance of the different client application, livecollaboration for the content item.
 17. The system of claim 16, whereinthe metadata comprises collaboration data generated during the livecollaboration session, and wherein providing live collaboration for thecontent item comprises presenting the collaboration data in associationwith the content item, the collaboration data identifying one or morelive collaboration communications or events.
 18. A non-transitorycomputer-readable medium comprising instructions that, when executed byone or more processors, cause the one or more processors to: receive arequest to open a content item using a client application at a firstclient device; detect that the content item is open at a second clientdevice from a different client application that supports livecollaboration; and direct the first client device to an instance of thedifferent client application at the first client device.
 19. Thenon-transitory computer-readable medium of claim 18, wherein directingthe first client device to the instance of the different clientapplication comprises routing a user account associated with the firstclient device to the instance of the different client application,opening the content item from the instance of the different clientapplication, and establishing a live collaboration session with a seconduser account associated with the second client device.
 20. Thenon-transitory computer-readable medium of claim 19, whereinestablishing the live collaboration session comprises: determining thata cloud service supports live collaboration for the content item;sending, from the instance of the different client application to thecloud service, a request for metadata associated with the livecollaboration session; receiving, at the instance of the differentclient application and from the cloud service, the metadata associatedwith the live collaboration session; and based on the metadata,providing, via the instance of the different client application, livecollaboration for the content item, wherein providing live collaborationfor the content item comprises presenting collaboration data inassociation with the content item, the collaboration data identifyingone or more live collaboration communications or events.